Tools & Wizards About Us

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

boots.com

Beauty | Health | Pharmacy and Prescriptions - Boots

Page Load Speed

6 sec in total

First Response

156 ms

Resources Loaded

2.6 sec

Page Rendered

3.3 sec

About Website

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

Shop our extensive range of health and beauty products from leading brands, fragrances for her and him and much more on Boots.com

Visit boots.com

Key Findings

We analyzed Boots.com page load time and found that the first response time was 156 ms and then it took 5.9 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

boots.com performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value17.7 s

0/100

25%

SI (Speed Index)

Value16.7 s

0/100

10%

TBT (Total Blocking Time)

Value9,020 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.401

25/100

15%

TTI (Time to Interactive)

Value30.6 s

0/100

10%

Network Requests Diagram

www.boots.com

156 ms

common.min.css

24 ms

algolia.min.css

19 ms

algolia.autocomplete.search.js

82 ms

visitor.js

127 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 63% of them (67 requests) were addressed to the original Boots.com, 12% (13 requests) were made to Cdn.synthetix.com and 6% (6 requests) were made to Assets.boots.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (53%)

Content Size

2.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Boots.com main page is 2.5 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. HTML takes 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 1.3 MB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 126.5 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 91% of the original size.

Image Optimization

-4%

Potential reduce by 10.3 kB

  • Original 249.2 kB
  • After minification 238.9 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. Boots images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 12.0 kB

  • Original 701.1 kB
  • After minification 701.1 kB
  • After compression 689.1 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

-0%

Potential reduce by 302 B

  • Original 108.1 kB
  • After minification 108.1 kB
  • After compression 107.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. Boots.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 71 (73%)

Requests Now

97

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

boots.com accessibility score

83

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

button, link, and menuitem elements do not have accessible names.

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

High

Some elements have a [tabindex] value greater than 0

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

boots.com best practices score

75

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

boots.com SEO score

86

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

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

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