Tools & Wizards About Us

Report Summary

  • 2

    Performance

    Renders faster than
    20% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

waitroseflorist.com

Fresh Flowers and Plants | Waitrose & Partners

Page Load Speed

22 sec in total

First Response

285 ms

Resources Loaded

20.6 sec

Page Rendered

1.2 sec

About Website

Visit waitroseflorist.com now to see the best up-to-date Waitrose Florist content for United Kingdom and also check out these interesting facts you probably never knew about waitroseflorist.com

See our selection of Fresh Flowers & Plants and buy quality Kitchen, Dining & Home online at Waitrose. Picked, packed and delivered by hand in convenient 1-hour slots.

Visit waitroseflorist.com

Key Findings

We analyzed Waitroseflorist.com page load time and found that the first response time was 285 ms and then it took 21.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

waitroseflorist.com performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value18.2 s

0/100

25%

SI (Speed Index)

Value14.7 s

1/100

10%

TBT (Total Blocking Time)

Value5,090 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.652

9/100

15%

TTI (Time to Interactive)

Value20.0 s

2/100

10%

Network Requests Diagram

www.waitroseflorist.com

285 ms

entry.js

60 ms

normalize.css

67 ms

jquery-ui-1.10.3.custom.min.css

75 ms

screen.css

86 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 8% of them (6 requests) were addressed to the original Waitroseflorist.com, 68% (53 requests) were made to D2ma0sm7bfpafd.cloudfront.net and 14% (11 requests) were made to S7g10.scene7.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Waitrose.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 404.4 kB (22%)

Content Size

1.9 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Waitroseflorist.com main page is 1.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. 75% 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. Images take 855.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 123.0 kB

  • Original 148.9 kB
  • After minification 125.7 kB
  • After compression 25.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. This page needs HTML code to be minified as it can gain 23.2 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 123.0 kB or 83% of the original size.

Image Optimization

-7%

Potential reduce by 56.4 kB

  • Original 855.3 kB
  • After minification 798.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. Waitrose Florist images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 211.9 kB

  • Original 718.1 kB
  • After minification 717.0 kB
  • After compression 506.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 211.9 kB or 30% of the original size.

CSS Optimization

-8%

Potential reduce by 13.0 kB

  • Original 156.3 kB
  • After minification 155.9 kB
  • After compression 143.2 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. Waitroseflorist.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 43 (61%)

Requests Now

71

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

waitroseflorist.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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

waitroseflorist.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

waitroseflorist.com SEO score

64

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Waitroseflorist.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Waitroseflorist.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 Waitrose Florist. 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: