Tools & Wizards About Us
hatstone.com screenshot

Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

hatstone.com

Hatstone Group - multi-jurisdictional legal and fiduciary

Page Load Speed

3.2 sec in total

First Response

1 sec

Resources Loaded

1.6 sec

Page Rendered

539 ms

hatstone.com screenshot

About Website

Click here to check amazing Hatstone content. Otherwise, check out these important facts you probably never knew about hatstone.com

Hatstone Group is a multi-jurisdictional legal and fiduciary group with offices in the BVI, Jersey, Ireland, London, Panama and South Africa.

Visit hatstone.com

Key Findings

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

Performance Metrics

hatstone.com performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

41/100

25%

SI (Speed Index)

Value4.5 s

73/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.043

99/100

15%

TTI (Time to Interactive)

Value7.9 s

44/100

10%

Network Requests Diagram

hatstone.com

1028 ms

css2

40 ms

css2

59 ms

app.13290d5467cef711c18c.css

336 ms

cookieconsent.min.css

173 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 47% of them (16 requests) were addressed to the original Hatstone.com, 41% (14 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Hatstone.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 512.6 kB (72%)

Content Size

715.3 kB

After Optimization

202.7 kB

  • HTML
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 156.2 kB

  • Original 194.1 kB
  • After minification 181.9 kB
  • After compression 37.9 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 156.2 kB or 80% of the original size.

JavaScript Optimization

-66%

Potential reduce by 298.4 kB

  • Original 450.0 kB
  • After minification 450.0 kB
  • After compression 151.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 298.4 kB or 66% of the original size.

CSS Optimization

-81%

Potential reduce by 58.0 kB

  • Original 71.2 kB
  • After minification 71.2 kB
  • After compression 13.2 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. Hatstone.com needs all CSS files to be minified and compressed as it can save up to 58.0 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (47%)

Requests Now

19

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hatstone.com

hatstone.com

1028 ms

css2

css2

40 ms

css2

css2

59 ms

app.13290d5467cef711c18c.css

app.13290d5467cef711c18c.css

336 ms

cookieconsent.min.css

cookieconsent.min.css

173 ms

js

js

80 ms

plyr.js

plyr.js

65 ms

chunk-vendors.625744b7893100a69d61.js

chunk-vendors.625744b7893100a69d61.js

204 ms

chunk-vendors.e03607363425ac642898.es5.js

chunk-vendors.e03607363425ac642898.es5.js

417 ms

app.f459eee755449316fc6b.js

app.f459eee755449316fc6b.js

164 ms

app.13290d5467cef711c18c.es5.js

app.13290d5467cef711c18c.es5.js

204 ms

cookieconsent.min.js

cookieconsent.min.js

268 ms

AdobeStock_560259685.webp

AdobeStock_560259685.webp

332 ms

20.webp

20.webp

190 ms

panama-hatstone.webp

panama-hatstone.webp

275 ms

GettyImages-572970507-5b76f58ec9e77c0025535cd4.webp

GettyImages-572970507-5b76f58ec9e77c0025535cd4.webp

276 ms

London-hatstone.webp

London-hatstone.webp

438 ms

shutterstock_727916200_2023-12-07-134632_dkgt.webp

shutterstock_727916200_2023-12-07-134632_dkgt.webp

540 ms

Rectangle-157605.webp

Rectangle-157605.webp

362 ms

13.webp

13.webp

524 ms

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_m07NSg.ttf

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_m07NSg.ttf

100 ms

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_qU7NSg.ttf

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_qU7NSg.ttf

116 ms

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_907NSg.ttf

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_907NSg.ttf

140 ms

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_KU7NSg.ttf

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_KU7NSg.ttf

149 ms

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_d0nNSg.ttf

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_d0nNSg.ttf

151 ms

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_TknNSg.ttf

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_TknNSg.ttf

149 ms

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_KUnNSg.ttf

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_KUnNSg.ttf

150 ms

LDIZaomQNQcsA88c7O9yZ4KMCoOg4KozySKCdSNG9OcqYQ0XCR_Q.ttf

LDIZaomQNQcsA88c7O9yZ4KMCoOg4KozySKCdSNG9OcqYQ0XCR_Q.ttf

75 ms

LDIZaomQNQcsA88c7O9yZ4KMCoOg4KozySKCdSNG9OcqYQ0lCR_Q.ttf

LDIZaomQNQcsA88c7O9yZ4KMCoOg4KozySKCdSNG9OcqYQ0lCR_Q.ttf

45 ms

LDIZaomQNQcsA88c7O9yZ4KMCoOg4KozySKCdSNG9OcqYQ17CR_Q.ttf

LDIZaomQNQcsA88c7O9yZ4KMCoOg4KozySKCdSNG9OcqYQ17CR_Q.ttf

45 ms

LDIZaomQNQcsA88c7O9yZ4KMCoOg4KozySKCdSNG9OcqYQ2lCR_Q.ttf

LDIZaomQNQcsA88c7O9yZ4KMCoOg4KozySKCdSNG9OcqYQ2lCR_Q.ttf

47 ms

LDIZaomQNQcsA88c7O9yZ4KMCoOg4KozySKCdSNG9OcqYQ37Dh_Q.ttf

LDIZaomQNQcsA88c7O9yZ4KMCoOg4KozySKCdSNG9OcqYQ37Dh_Q.ttf

47 ms

LDIZaomQNQcsA88c7O9yZ4KMCoOg4KozySKCdSNG9OcqYQ3CDh_Q.ttf

LDIZaomQNQcsA88c7O9yZ4KMCoOg4KozySKCdSNG9OcqYQ3CDh_Q.ttf

47 ms

LDIZaomQNQcsA88c7O9yZ4KMCoOg4KozySKCdSNG9OcqYQ2lDh_Q.ttf

LDIZaomQNQcsA88c7O9yZ4KMCoOg4KozySKCdSNG9OcqYQ2lDh_Q.ttf

46 ms

Accessibility Review

hatstone.com accessibility score

82

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

[id] attributes on active, focusable elements are not unique

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

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

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

Page has valid source maps

SEO Factors

hatstone.com SEO score

86

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

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

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

hatstone.com

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