Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

jlt.co.nz

Marsh | Global Leader in Insurance Broking and Risk Management

Page Load Speed

3.5 sec in total

First Response

373 ms

Resources Loaded

2.3 sec

Page Rendered

817 ms

jlt.co.nz screenshot

About Website

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

Marsh is a global leader in insurance broking and risk management, bringing global, national, and industry-specific solutions.

Visit jlt.co.nz

Key Findings

We analyzed Jlt.co.nz page load time and found that the first response time was 373 ms and then it took 3.1 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

jlt.co.nz performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value16.2 s

0/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value2,000 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.092

92/100

15%

TTI (Time to Interactive)

Value23.6 s

1/100

10%

Network Requests Diagram

jlt.co.nz

373 ms

home.html

194 ms

clientlib-base.min.70267407c54bfd3d524dbb8e5bf56862.css

79 ms

clientlibrarymanager.min.4066faea2c14fde8235ed95b86add70c.js

220 ms

launch-cc6ba730465a.min.js

23 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Jlt.co.nz, 81% (47 requests) were made to Marsh.com and 3% (2 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Marsh.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 331.6 kB (7%)

Content Size

5.1 MB

After Optimization

4.7 MB

In fact, the total size of Jlt.co.nz main page is 5.1 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. 55% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 97.2 kB

  • Original 113.8 kB
  • After minification 96.3 kB
  • After compression 16.6 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 17.5 kB, which is 15% 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 97.2 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 88.7 kB

  • Original 4.5 MB
  • After minification 4.4 MB

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. Jlt images are well optimized though.

JavaScript Optimization

-43%

Potential reduce by 145.3 kB

  • Original 340.8 kB
  • After minification 340.8 kB
  • After compression 195.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 145.3 kB or 43% of the original size.

CSS Optimization

-0%

Potential reduce by 424 B

  • Original 131.0 kB
  • After minification 131.0 kB
  • After compression 130.6 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. Jlt.co.nz has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 32 (59%)

Requests Now

54

After Optimization

22

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

Accessibility Review

jlt.co.nz accessibility score

84

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.

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

Links do not have a discernible name

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

jlt.co.nz best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

jlt.co.nz SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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 Jlt.co.nz 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 Jlt.co.nz 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 Jlt. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: