Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

broking.co.uk

Insurance Age – Intelligence for the insurance broker community

Page Load Speed

3.4 sec in total

First Response

236 ms

Resources Loaded

2.8 sec

Page Rendered

374 ms

broking.co.uk screenshot

About Website

Visit broking.co.uk now to see the best up-to-date Broking content and also check out these interesting facts you probably never knew about broking.co.uk

Through exclusive news stories, analysis, interviews and features, Insurance Age delivers the market intelligence brokers need to improve their business.

Visit broking.co.uk

Key Findings

We analyzed Broking.co.uk page load time and found that the first response time was 236 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

broking.co.uk performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value1,430 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.132

81/100

15%

TTI (Time to Interactive)

Value19.2 s

2/100

10%

Network Requests Diagram

broking.co.uk

236 ms

www.insuranceage.nqlnginx.incbase.net

239 ms

www.insuranceage.co.uk

624 ms

broking.css

306 ms

article.css

310 ms

Our browser made a total of 137 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Broking.co.uk, 53% (72 requests) were made to Insuranceage.co.uk and 4% (6 requests) were made to Incisivemedia.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Insuranceage.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 794.0 kB (46%)

Content Size

1.7 MB

After Optimization

918.5 kB

In fact, the total size of Broking.co.uk main page is 1.7 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. 60% of websites need less resources to load. Javascripts take 853.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 87.4 kB

  • Original 108.6 kB
  • After minification 92.9 kB
  • After compression 21.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 15.7 kB, which is 14% 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 87.4 kB or 80% of the original size.

Image Optimization

-7%

Potential reduce by 42.8 kB

  • Original 637.3 kB
  • After minification 594.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. Broking images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 571.7 kB

  • Original 853.6 kB
  • After minification 843.8 kB
  • After compression 281.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 571.7 kB or 67% of the original size.

CSS Optimization

-81%

Potential reduce by 92.0 kB

  • Original 113.0 kB
  • After minification 98.0 kB
  • After compression 20.9 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. Broking.co.uk needs all CSS files to be minified and compressed as it can save up to 92.0 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 72 (55%)

Requests Now

130

After Optimization

58

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

Accessibility Review

broking.co.uk accessibility score

75

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

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

broking.co.uk 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

Missing source maps for large first-party JavaScript

SEO Factors

broking.co.uk SEO score

83

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

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 Broking.co.uk 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 Broking.co.uk 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 Broking. 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: