Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

walgreens.com

Walgreens: Pharmacy, Health & Wellness, Photo & More for You

Page Load Speed

7.1 sec in total

First Response

1.3 sec

Resources Loaded

2.4 sec

Page Rendered

3.3 sec

About Website

Welcome to walgreens.com homepage info - get ready to check Walgreens best content for United States right away, or after learning these important things about walgreens.com

Your go-to for Pharmacy, Health & Wellness and Photo products. Refill prescriptions online, order items for delivery or store pickup, and create Photo Gifts.

Visit walgreens.com

Key Findings

We analyzed Walgreens.com page load time and found that the first response time was 1.3 sec and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

walgreens.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value7,180 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.052

99/100

15%

TTI (Time to Interactive)

Value28.1 s

0/100

10%

Network Requests Diagram

www.walgreens.com

1289 ms

lsg-common.css

109 ms

gpt.js

162 ms

gpt_common_v5.js

28 ms

css2

67 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 74% of them (79 requests) were addressed to the original Walgreens.com, 10% (11 requests) were made to Wag-static.com and 6% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Walgreens.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.1 MB (42%)

Content Size

4.9 MB

After Optimization

2.9 MB

In fact, the total size of Walgreens.com main page is 4.9 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 927.3 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 178.1 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 927.3 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 49.9 kB

  • Original 1.8 MB
  • After minification 1.7 MB

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. Walgreens images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 1.1 MB

  • Original 2.0 MB
  • After minification 2.0 MB
  • After compression 932.7 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 1.1 MB or 54% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (18%)

Requests Now

96

After Optimization

79

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

Accessibility Review

walgreens.com accessibility score

96

Accessibility Issues

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

walgreens.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

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

Missing source maps for large first-party JavaScript

SEO Factors

walgreens.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    \

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Walgreens.com 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 Walgreens.com main page’s claimed encoding is \. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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