Access alexmswainsbury.com.

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value1,050 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.278

44/100

15%

TTI (Time to Interactive)

Value19.2 s

2/100

10%

alexmswainsbury.com

30 ms

alexmswainsbury.com

133 ms

120 ms

react.production.min.js

20 ms

react-dom.production.min.js

18 ms

Our browser made a total of 6 requests to load all elements on the main page. We found that 33% of them (2 requests) were addressed to the original Alexmswainsbury.com, 67% (4 requests) were made to Northwesternmutual.com. The less responsive or slowest element that took the longest time to load (133 ms) belongs to the original domain Alexmswainsbury.com.

Content Size

751.8 kB

After Optimization

674.3 kB

In fact, the total size of Alexmswainsbury.com main page is 751.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. Only 5% of websites need less resources to load. Javascripts take 651.6 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 77.5 kB

Original 100.2 kB
After minification 100.1 kB
After compression 22.7 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 77.5 kB or 77% of the original size.

JavaScript Optimization

-0%

Potential reduce by 18 B

Original 651.6 kB
After minification 651.6 kB
After compression 651.6 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 Now

After Optimization

The browser has sent 3 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Alexmswainsbury. According to our analytics all requests are already optimized.

Accessibility Issues

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.

High

[role]s are not contained by their required parent element

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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