Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

thomaseggar.com

Irwin Mitchell Solicitors | Personal & Business Legal Services

Page Load Speed

3.1 sec in total

First Response

600 ms

Resources Loaded

1.6 sec

Page Rendered

855 ms

thomaseggar.com screenshot

About Website

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

If you or your business need legal advice, we’re here. Our solicitors and advisers will listen and give you all the support you need.

Visit thomaseggar.com

Key Findings

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

Performance Metrics

thomaseggar.com performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

58/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value660 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

www.irwinmitchell.com

600 ms

VisitorIdentification.js

14 ms

tp.widget.bootstrap.min.js

20 ms

j.php

50 ms

CookieConsentBanner3.2.js

23 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Thomaseggar.com, 22% (13 requests) were made to Irwinmitchell.com and 14% (8 requests) were made to Cdn.yoshki.com. The less responsive or slowest element that took the longest time to load (600 ms) relates to the external source Irwinmitchell.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 368.8 kB (28%)

Content Size

1.3 MB

After Optimization

946.7 kB

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

HTML Optimization

-87%

Potential reduce by 235.0 kB

  • Original 270.2 kB
  • After minification 206.4 kB
  • After compression 35.2 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 63.8 kB, which is 24% 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 235.0 kB or 87% of the original size.

Image Optimization

-4%

Potential reduce by 10.2 kB

  • Original 254.7 kB
  • After minification 244.5 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. Thomaseggar images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 67.8 kB

  • Original 708.9 kB
  • After minification 708.8 kB
  • After compression 641.0 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

-68%

Potential reduce by 55.8 kB

  • Original 81.8 kB
  • After minification 81.7 kB
  • After compression 26.0 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. Thomaseggar.com needs all CSS files to be minified and compressed as it can save up to 55.8 kB or 68% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (74%)

Requests Now

54

After Optimization

14

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

Accessibility Review

thomaseggar.com accessibility score

98

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.

Best Practices

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

High

Page has valid source maps

SEO Factors

thomaseggar.com SEO score

92

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thomaseggar.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 Thomaseggar.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 data is detected on the main page of Thomaseggar. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: