Tools & Wizards About Us
alexmswainsbury.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

alexmswainsbury.com

Page Load Speed

556 ms in total

First Response

30 ms

Resources Loaded

471 ms

Page Rendered

55 ms

alexmswainsbury.com screenshot

About Website

Welcome to alexmswainsbury.com homepage info - get ready to check Alexmswainsbury best content right away, or after learning these important things about alexmswainsbury.com

Visit alexmswainsbury.com

Key Findings

We analyzed Alexmswainsbury.com page load time and found that the first response time was 30 ms and then it took 526 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

alexmswainsbury.com performance score

17

Measured Metrics

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%

Network Requests Diagram

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.

Page Optimization Overview & Recommendations

Page size can be reduced by 77.6 kB (10%)

Content Size

751.9 kB

After Optimization

674.3 kB

  • HTML
  • JavaScript

In fact, the total size of Alexmswainsbury.com main page is 751.9 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.7 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 73 B

  • Original 651.7 kB
  • After minification 651.7 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 Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

  • JavaScript

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.

Network Requests Diagram

alexmswainsbury.com

alexmswainsbury.com

30 ms

alexmswainsbury.com

alexmswainsbury.com

133 ms

120 ms

react.production.min.js

react.production.min.js

20 ms

react-dom.production.min.js

react-dom.production.min.js

18 ms

bundle.js

bundle.js

30 ms

Accessibility Review

alexmswainsbury.com accessibility score

90

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

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

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

Best Practices

alexmswainsbury.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

alexmswainsbury.com SEO score

98

Search Engine Optimization Advices

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

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

alexmswainsbury.com

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: