Tools & Wizards About Us
brittontime.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

brittontime.com

Award Winning Solicitors in London and Brighton | Britton & Time

Page Load Speed

2.4 sec in total

First Response

656 ms

Resources Loaded

1.3 sec

Page Rendered

452 ms

brittontime.com screenshot

About Website

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

Leading solicitors in London and Brighton offering personal and business legal services across Brighton and Hove, Sussex and the wider South East. Whatever your matter, we're here to help.

Visit brittontime.com

Key Findings

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

Performance Metrics

brittontime.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value10.5 s

8/100

10%

TBT (Total Blocking Time)

Value1,560 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.835

4/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

brittontime.com

656 ms

css

33 ms

cookie-law-info-public.css

21 ms

cookie-law-info-gdpr.css

21 ms

light-box-styles.css

22 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 60% of them (44 requests) were addressed to the original Brittontime.com, 38% (28 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (656 ms) belongs to the original domain Brittontime.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 338.6 kB (85%)

Content Size

397.9 kB

After Optimization

59.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Brittontime.com main page is 397.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. 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. HTML takes 394.3 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 338.6 kB

  • Original 394.3 kB
  • After minification 385.5 kB
  • After compression 55.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 338.6 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.9 kB
  • After minification 2.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. Britton Time images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 17 B

  • Original 655 B
  • After minification 655 B
  • After compression 638 B

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

Number of requests can be reduced by 39 (91%)

Requests Now

43

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

brittontime.com

brittontime.com

656 ms

css

css

33 ms

cookie-law-info-public.css

cookie-law-info-public.css

21 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

21 ms

light-box-styles.css

light-box-styles.css

22 ms

swiper.min.css

swiper.min.css

24 ms

df-style.css

df-style.css

22 ms

magnific_popup.css

magnific_popup.css

29 ms

animate.css

animate.css

28 ms

pagenavi-css.css

pagenavi-css.css

32 ms

style.min.css

style.min.css

31 ms

style.min.css

style.min.css

32 ms

style.min.css

style.min.css

43 ms

style-static.min.css

style-static.min.css

50 ms

style.css

style.css

38 ms

jquery.js

jquery.js

96 ms

jquery-migrate.js

jquery-migrate.js

49 ms

cookie-law-info-public.js

cookie-law-info-public.js

127 ms

slick.js

slick.js

162 ms

email-decode.min.js

email-decode.min.js

127 ms

rs.js

rs.js

162 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

126 ms

wp-mediaelement.css

wp-mediaelement.css

127 ms

cookie-law-info-table.css

cookie-law-info-table.css

449 ms

swiper.min.js

swiper.min.js

128 ms

Britton-and-Time-Solicitors-in-Brighton-and-Hove.png

Britton-and-Time-Solicitors-in-Brighton-and-Hove.png

131 ms

df-script.js

df-script.js

131 ms

scripts.min.js

scripts.min.js

131 ms

smoothscroll.js

smoothscroll.js

129 ms

es6-promise.auto.min.js

es6-promise.auto.min.js

131 ms

recaptcha.js

recaptcha.js

132 ms

frontend-bundle.min.js

frontend-bundle.min.js

132 ms

frontend-bundle.min.js

frontend-bundle.min.js

133 ms

frontend-bundle.min.js

frontend-bundle.min.js

132 ms

common.js

common.js

134 ms

mediaelement-and-player.js

mediaelement-and-player.js

133 ms

mediaelement-migrate.js

mediaelement-migrate.js

134 ms

wp-mediaelement.js

wp-mediaelement.js

134 ms

salvattore.js

salvattore.js

134 ms

jquery.fitvids.js

jquery.fitvids.js

134 ms

jquery.mobile.js

jquery.mobile.js

434 ms

easypiechart.js

easypiechart.js

135 ms

lazyload.js

lazyload.js

134 ms

subscribe-loader.gif

subscribe-loader.gif

538 ms

font

font

86 ms

KFOkCnqEu92Fr1MmgVxGIzc.ttf

KFOkCnqEu92Fr1MmgVxGIzc.ttf

161 ms

KFOlCnqEu92Fr1MmSU5fChc-.woff

KFOlCnqEu92Fr1MmSU5fChc-.woff

184 ms

KFOlCnqEu92Fr1MmSU5fChc9.ttf

KFOlCnqEu92Fr1MmSU5fChc9.ttf

183 ms

KFOmCnqEu92Fr1Mu7GxM.woff

KFOmCnqEu92Fr1Mu7GxM.woff

183 ms

KFOmCnqEu92Fr1Mu7GxP.ttf

KFOmCnqEu92Fr1Mu7GxP.ttf

186 ms

KFOlCnqEu92Fr1MmEU9fChc-.woff

KFOlCnqEu92Fr1MmEU9fChc-.woff

183 ms

KFOlCnqEu92Fr1MmEU9fChc9.ttf

KFOlCnqEu92Fr1MmEU9fChc9.ttf

185 ms

KFOlCnqEu92Fr1MmWUlfChc-.woff

KFOlCnqEu92Fr1MmWUlfChc-.woff

186 ms

KFOlCnqEu92Fr1MmWUlfChc9.ttf

KFOlCnqEu92Fr1MmWUlfChc9.ttf

184 ms

KFOlCnqEu92Fr1MmYUtfChc-.woff

KFOlCnqEu92Fr1MmYUtfChc-.woff

184 ms

KFOlCnqEu92Fr1MmYUtfChc9.ttf

KFOlCnqEu92Fr1MmYUtfChc9.ttf

185 ms

font

font

177 ms

J7acnpd8CGxBHp2VkaYxzps.ttf

J7acnpd8CGxBHp2VkaYxzps.ttf

141 ms

J7aRnpd8CGxBHpUgtLU.woff

J7aRnpd8CGxBHpUgtLU.woff

142 ms

J7aRnpd8CGxBHpUgtLY.ttf

J7aRnpd8CGxBHpUgtLY.ttf

142 ms

modules.woff

modules.woff

100 ms

KFOiCnqEu92Fr1Mu51QrEz4dKQ.woff

KFOiCnqEu92Fr1Mu51QrEz4dKQ.woff

106 ms

KFOiCnqEu92Fr1Mu51QrEz4dKg.ttf

KFOiCnqEu92Fr1Mu51QrEz4dKg.ttf

106 ms

KFOjCnqEu92Fr1Mu51TjASc0CsI.woff

KFOjCnqEu92Fr1Mu51TjASc0CsI.woff

107 ms

KFOjCnqEu92Fr1Mu51TjASc0CsE.ttf

KFOjCnqEu92Fr1Mu51TjASc0CsE.ttf

108 ms

KFOkCnqEu92Fr1Mu51xGIzQ.woff

KFOkCnqEu92Fr1Mu51xGIzQ.woff

135 ms

KFOkCnqEu92Fr1Mu51xGIzc.ttf

KFOkCnqEu92Fr1Mu51xGIzc.ttf

135 ms

KFOjCnqEu92Fr1Mu51S7ACc0CsI.woff

KFOjCnqEu92Fr1Mu51S7ACc0CsI.woff

135 ms

KFOjCnqEu92Fr1Mu51S7ACc0CsE.ttf

KFOjCnqEu92Fr1Mu51S7ACc0CsE.ttf

136 ms

KFOjCnqEu92Fr1Mu51TzBic0CsI.woff

KFOjCnqEu92Fr1Mu51TzBic0CsI.woff

136 ms

KFOjCnqEu92Fr1Mu51TzBic0CsE.ttf

KFOjCnqEu92Fr1Mu51TzBic0CsE.ttf

137 ms

KFOjCnqEu92Fr1Mu51TLBCc0CsI.woff

KFOjCnqEu92Fr1Mu51TLBCc0CsI.woff

138 ms

KFOjCnqEu92Fr1Mu51TLBCc0CsE.ttf

KFOjCnqEu92Fr1Mu51TLBCc0CsE.ttf

137 ms

Accessibility Review

brittontime.com accessibility score

86

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

SEO Factors

brittontime.com SEO score

91

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

brittontime.com

Open Graph data is detected on the main page of Britton Time. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: