Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

walgreenslistens.page

WalgreensListens - Take www.walgreenslistens.com Survey

Page Load Speed

3.6 sec in total

First Response

331 ms

Resources Loaded

2.9 sec

Page Rendered

361 ms

About Website

Welcome to walgreenslistens.page homepage info - get ready to check Walgreens Listens best content right away, or after learning these important things about walgreenslistens.page

WalgreensListens Survey provides a chance to win $3000 Cash which is available on the www.walgreenslistens.com official website (Walgreens Listens)

Visit walgreenslistens.page

Key Findings

We analyzed Walgreenslistens.page page load time and found that the first response time was 331 ms and then it took 3.3 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

walgreenslistens.page performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value1,720 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.3 s

25/100

10%

Network Requests Diagram

walgreenslistens.page

331 ms

www.walgreenslistens.page

345 ms

www.walgreenslistens.run

336 ms

style.min.css

306 ms

styles.css

314 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Walgreenslistens.page, 42% (19 requests) were made to Walgreenslistens.run and 13% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (926 ms) relates to the external source Walgreenslistens.run.

Page Optimization Overview & Recommendations

Page size can be reduced by 46.7 kB (7%)

Content Size

656.5 kB

After Optimization

609.8 kB

In fact, the total size of Walgreenslistens.page main page is 656.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 443.4 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 43.5 kB

  • Original 57.9 kB
  • After minification 57.4 kB
  • After compression 14.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 43.5 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 793 B

  • Original 129.2 kB
  • After minification 128.4 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. Walgreens Listens images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 2.2 kB

  • Original 443.4 kB
  • After minification 443.3 kB
  • After compression 441.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 231 B

  • Original 26.0 kB
  • After minification 26.0 kB
  • After compression 25.8 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Walgreenslistens.page has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 25 (63%)

Requests Now

40

After Optimization

15

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

Accessibility Review

walgreenslistens.page accessibility score

92

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

<frame> or <iframe> elements do not have a title

Best Practices

walgreenslistens.page best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

walgreenslistens.page SEO score

100

Search Engine Optimization Advices

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

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 Walgreenslistens.page 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 Walgreenslistens.page 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 data is detected on the main page of Walgreens Listens. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: