Report Summary

  • 2

    Performance

    Renders faster than
    19% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

weeklyad.walgreens.com

Weekly Ad | Walgreens

Page Load Speed

2 sec in total

First Response

256 ms

Resources Loaded

1.4 sec

Page Rendered

315 ms

weeklyad.walgreens.com screenshot

About Website

Click here to check amazing Weekly Ad Walgreens content for United States. Otherwise, check out these important facts you probably never knew about weeklyad.walgreens.com

The Walgreens Weekly Ad on Walgreens.com. Clip this week's coupons online and see all sales happening at your local Walgreens. Start saving with the Walgreens Weekly Ad!

Visit weeklyad.walgreens.com

Key Findings

We analyzed Weeklyad.walgreens.com page load time and found that the first response time was 256 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

weeklyad.walgreens.com performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value26.3 s

0/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value8,110 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.804

5/100

15%

TTI (Time to Interactive)

Value34.4 s

0/100

10%

Network Requests Diagram

weeklyad.walgreens.com

256 ms

default.aspx

23 ms

189 ms

offers.jsp

516 ms

ruxitagentjs_ICANVfghqrux_10289240325103055.js

54 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Weeklyad.walgreens.com, 65% (20 requests) were made to Walgreens.com and 10% (3 requests) were made to Wag-static.com. The less responsive or slowest element that took the longest time to load (516 ms) relates to the external source Walgreens.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.3 MB (71%)

Content Size

3.2 MB

After Optimization

938.7 kB

In fact, the total size of Weeklyad.walgreens.com main page is 3.2 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. 80% 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. HTML takes 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 1.3 MB

  • Original 1.7 MB
  • After minification 1.6 MB
  • After compression 385.6 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.3 MB or 77% of the original size.

Image Optimization

-8%

Potential reduce by 3.4 kB

  • Original 42.9 kB
  • After minification 39.5 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. Weekly Ad Walgreens images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 1.0 MB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 513.6 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.0 MB or 67% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (59%)

Requests Now

27

After Optimization

11

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weekly Ad 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 17 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

weeklyad.walgreens.com accessibility score

87

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Best Practices

weeklyad.walgreens.com best practices score

50

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

weeklyad.walgreens.com SEO score

78

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weeklyad.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 Weeklyad.walgreens.com 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

Open Graph description is not detected on the main page of Weekly Ad Walgreens. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: