Tools & Wizards About Us
pharmeasy.in screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

pharmeasy.in

PharmEasy: Online Pharmacy & Medical Store in India | 50 Lakhs+ Customers.

Page Load Speed

3.3 sec in total

First Response

22 ms

Resources Loaded

1.3 sec

Page Rendered

2 sec

pharmeasy.in screenshot

About Website

Welcome to pharmeasy.in homepage info - get ready to check Pharm Easy best content for India right away, or after learning these important things about pharmeasy.in

PharmEasy is one of India's most trusted online pharmacy & medical stores offering pharmaceutical and healthcare products at a FLAT 20% OFF*. Used by 50 lakhs+ customers in India in 1200+ cit...

Visit pharmeasy.in

Key Findings

We analyzed Pharmeasy.in page load time and found that the first response time was 22 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

pharmeasy.in performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

86/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value9,430 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value20.3 s

2/100

10%

Network Requests Diagram

pharmeasy.in

22 ms

pharmeasy.in

195 ms

eum.min.js

129 ms

polyfills-5cd94c89d3acac5f.js

306 ms

webpack-916fd3f3d4c0928c.js

346 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 13% of them (3 requests) were addressed to the original Pharmeasy.in, 78% (18 requests) were made to Assets.pharmeasy.in and 4% (1 request) were made to Eum.instana.io. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Cdn01.pharmeasy.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (75%)

Content Size

2.1 MB

After Optimization

518.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Pharmeasy.in main page is 2.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. HTML takes 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 1.0 MB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 117.4 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 1.0 MB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 88.8 kB
  • After minification 88.8 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Pharm Easy images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 498.4 kB

  • Original 810.8 kB
  • After minification 810.8 kB
  • After compression 312.4 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 498.4 kB or 61% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (52%)

Requests Now

21

After Optimization

10

  • Images
  • JavaScript

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pharm Easy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

pharmeasy.in

pharmeasy.in

22 ms

pharmeasy.in

pharmeasy.in

195 ms

eum.min.js

eum.min.js

129 ms

polyfills-5cd94c89d3acac5f.js

polyfills-5cd94c89d3acac5f.js

306 ms

webpack-916fd3f3d4c0928c.js

webpack-916fd3f3d4c0928c.js

346 ms

framework-0c5c477e14244402.js

framework-0c5c477e14244402.js

478 ms

main-4d1cb1d9c2105bea.js

main-4d1cb1d9c2105bea.js

559 ms

_app-d94c162f6adb0f73.js

_app-d94c162f6adb0f73.js

462 ms

1318-ffd6fd3625f64f7b.js

1318-ffd6fd3625f64f7b.js

455 ms

index-015dbd1191dde248.js

index-015dbd1191dde248.js

414 ms

_buildManifest.js

_buildManifest.js

395 ms

_ssgManifest.js

_ssgManifest.js

446 ms

_middlewareManifest.js

_middlewareManifest.js

503 ms

ae1aca67b0a-24PHARMA_MM_HP.jpg

ae1aca67b0a-24PHARMA_MM_HP.jpg

1147 ms

logo_big.svg

logo_big.svg

480 ms

ic_order_med.svg

ic_order_med.svg

484 ms

ic_labtest.svg

ic_labtest.svg

466 ms

ic_healthcare_products.svg

ic_healthcare_products.svg

513 ms

ic_blogs.svg

ic_blogs.svg

551 ms

ic_plus_ff.svg

ic_plus_ff.svg

500 ms

ic_offers.svg

ic_offers.svg

550 ms

Q_E2V0UTU

Q_E2V0UTU

80 ms

spotlightBig.svg

spotlightBig.svg

488 ms

Accessibility Review

pharmeasy.in accessibility score

82

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

pharmeasy.in best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

pharmeasy.in SEO score

89

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pharmeasy.in can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Pharmeasy.in main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

pharmeasy.in

Open Graph data is detected on the main page of Pharm Easy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: