Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

expressgrass.com

expressgrass™ - Artificial Grass - Next Working Day Delivery across the UK.

Page Load Speed

7.6 sec in total

First Response

134 ms

Resources Loaded

6.8 sec

Page Rendered

730 ms

expressgrass.com screenshot

About Website

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

DIY Artificial Grass and Astro turf supplied overnight to UK Gardeners, Landscapers & Retailers across England, Scotland and Wales. Start your artificial grass transformation today with expressgrass.c...

Visit expressgrass.com

Key Findings

We analyzed Expressgrass.com page load time and found that the first response time was 134 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

expressgrass.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value50.8 s

0/100

10%

TBT (Total Blocking Time)

Value58,680 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value92.9 s

0/100

10%

Network Requests Diagram

expressgrass.com

134 ms

expressgrass.com

927 ms

4f0bbb410fe6aa5b7388e8944d957eef.css

235 ms

styles-l.css

419 ms

2b0fb6bc60cc0d482995db9fdb796907.js

446 ms

Our browser made a total of 360 requests to load all elements on the main page. We found that 83% of them (299 requests) were addressed to the original Expressgrass.com, 7% (26 requests) were made to Staticw2.yotpo.com and 2% (7 requests) were made to P.yotpo.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Expressgrass.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 723.1 kB (36%)

Content Size

2.0 MB

After Optimization

1.3 MB

In fact, the total size of Expressgrass.com main page is 2.0 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. Javascripts take 705.4 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 404.4 kB

  • Original 457.9 kB
  • After minification 404.7 kB
  • After compression 53.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. This page needs HTML code to be minified as it can gain 53.2 kB, which is 12% 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 404.4 kB or 88% of the original size.

Image Optimization

-4%

Potential reduce by 22.9 kB

  • Original 627.0 kB
  • After minification 604.1 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. Express Grass images are well optimized though.

JavaScript Optimization

-39%

Potential reduce by 272.5 kB

  • Original 705.4 kB
  • After minification 673.4 kB
  • After compression 432.9 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 272.5 kB or 39% of the original size.

CSS Optimization

-11%

Potential reduce by 23.3 kB

  • Original 215.0 kB
  • After minification 215.0 kB
  • After compression 191.7 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. Expressgrass.com needs all CSS files to be minified and compressed as it can save up to 23.3 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 269 (78%)

Requests Now

345

After Optimization

76

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

Accessibility Review

expressgrass.com accessibility score

78

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.

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 IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

expressgrass.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Expressgrass.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 Expressgrass.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 Express Grass. 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: