Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

employee.walgreens.com

WBA Worldwide | Login

Page Load Speed

1.8 sec in total

First Response

179 ms

Resources Loaded

1.5 sec

Page Rendered

97 ms

employee.walgreens.com screenshot

About Website

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

Visit employee.walgreens.com

Key Findings

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

Performance Metrics

employee.walgreens.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value700 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.116

85/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

employee.walgreens.com

179 ms

login

320 ms

ruxitagentjs_ICANVfhqru_10289240325103055.js

204 ms

main.css

41 ms

mentions.css

49 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Employee.walgreens.com, 89% (32 requests) were made to Wbaww-pro.azureedge.net and 6% (2 requests) were made to Wbaworldwide.wba.com. The less responsive or slowest element that took the longest time to load (320 ms) relates to the external source Wbaworldwide.wba.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 84.4 kB (17%)

Content Size

490.8 kB

After Optimization

406.4 kB

In fact, the total size of Employee.walgreens.com main page is 490.8 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. 70% of websites need less resources to load. Javascripts take 341.7 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 58.0 kB

  • Original 70.8 kB
  • After minification 66.2 kB
  • After compression 12.8 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 58.0 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 17 B

  • Original 78.4 kB
  • After minification 78.3 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. Employee Walgreens images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 26.4 kB

  • Original 341.7 kB
  • After minification 341.7 kB
  • After compression 315.3 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.

Requests Breakdown

Number of requests can be reduced by 24 (86%)

Requests Now

28

After Optimization

4

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

Accessibility Review

employee.walgreens.com accessibility score

97

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.

Best Practices

employee.walgreens.com 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

SEO Factors

employee.walgreens.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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 Employee.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 Employee.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 Employee 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: