Tools & Wizards About Us
yorkestone.co.nz screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

yorkestone.co.nz

Yorke Stone & Associates - Chartered Accountants Whangarei

Page Load Speed

5.9 sec in total

First Response

484 ms

Resources Loaded

5.4 sec

Page Rendered

76 ms

yorkestone.co.nz screenshot

About Website

Welcome to yorkestone.co.nz homepage info - get ready to check Yorke Stone best content right away, or after learning these important things about yorkestone.co.nz

Our team provide accountancy and business advisory services to clients across Northland, the North and South Islands of New Zealand and overseas. We bring the values of Loyalty and Integrity as we map...

Visit yorkestone.co.nz

Key Findings

We analyzed Yorkestone.co.nz page load time and found that the first response time was 484 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

yorkestone.co.nz performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

2/100

10%

LCP (Largest Contentful Paint)

Value20.8 s

0/100

25%

SI (Speed Index)

Value15.0 s

1/100

10%

TBT (Total Blocking Time)

Value2,990 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.086

93/100

15%

TTI (Time to Interactive)

Value26.9 s

0/100

10%

Network Requests Diagram

yorkestone.co.nz

484 ms

yorkestone.co.nz

1170 ms

js

70 ms

css

599 ms

js

1575 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 69% of them (48 requests) were addressed to the original Yorkestone.co.nz, 20% (14 requests) were made to Static.xx.fbcdn.net and 3% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Yorkestone.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 126.5 kB (3%)

Content Size

4.0 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yorkestone.co.nz main page is 4.0 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. 80% 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. Images take 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 60.1 kB

  • Original 76.0 kB
  • After minification 67.9 kB
  • After compression 15.8 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 8.1 kB, which is 11% 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 60.1 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 51.1 kB

  • Original 3.3 MB
  • After minification 3.2 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. Yorke Stone images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 15.3 kB

  • Original 599.0 kB
  • After minification 599.0 kB
  • After compression 583.7 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

-0%

Potential reduce by 0 B

  • Original 83.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.

Requests Breakdown

Number of requests can be reduced by 23 (38%)

Requests Now

61

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yorke Stone. 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 as a result speed up the page load time.

Network Requests Diagram

yorkestone.co.nz

yorkestone.co.nz

484 ms

yorkestone.co.nz

yorkestone.co.nz

1170 ms

js

js

70 ms

css

css

599 ms

js

js

1575 ms

WebResource.axd

WebResource.axd

794 ms

ScriptResource.axd

ScriptResource.axd

1019 ms

ScriptResource.axd

ScriptResource.axd

825 ms

js

js

1426 ms

4ef0995045.js

4ef0995045.js

86 ms

WebResource.axd

WebResource.axd

631 ms

WebResource.axd

WebResource.axd

798 ms

WebResource.axd

WebResource.axd

832 ms

WebResource.axd

WebResource.axd

833 ms

api.js

api.js

36 ms

YSA%20-%20LOGO%20-%20Mana%20-%20Landscape%20-%202024.png

YSA%20-%20LOGO%20-%20Mana%20-%20Landscape%20-%202024.png

389 ms

4135danmug.jpg

4135danmug.jpg

260 ms

4136nancy.jpg

4136nancy.jpg

260 ms

5780tui.jpg

5780tui.jpg

259 ms

5781flynn.jpg

5781flynn.jpg

260 ms

4533pauline.jpg

4533pauline.jpg

241 ms

4531LisaYoungClientServicesAccounant.jpg

4531LisaYoungClientServicesAccounant.jpg

390 ms

4532IMG_20220202_211517resz.jpg

4532IMG_20220202_211517resz.jpg

443 ms

5782tash.jpg

5782tash.jpg

444 ms

loading.gif

loading.gif

836 ms

go.png

go.png

442 ms

Xerox230x230.jpg

Xerox230x230.jpg

625 ms

Auditx230x230.jpg

Auditx230x230.jpg

625 ms

MMPx230x230.jpg

MMPx230x230.jpg

659 ms

SLAVisoryx230x230.jpg

SLAVisoryx230x230.jpg

659 ms

TABx230x230.jpg

TABx230x230.jpg

658 ms

thegapx230x230.jpg

thegapx230x230.jpg

775 ms

CA-ANZ-Logox230x230.png

CA-ANZ-Logox230x230.png

776 ms

icon.png

icon.png

838 ms

gfmweb.png

gfmweb.png

838 ms

welcomeside.jpg

welcomeside.jpg

998 ms

welcomeover.jpg

welcomeover.jpg

1126 ms

servicesv3.jpg

servicesv3.jpg

1514 ms

over.jpg

over.jpg

1787 ms

Circe-Regular.woff

Circe-Regular.woff

1441 ms

Circe-Light.woff

Circe-Light.woff

1452 ms

Circe-ExtraLight.woff

Circe-ExtraLight.woff

1241 ms

Circe-Bold.woff

Circe-Bold.woff

1320 ms

Circe-ExtraBold.woff

Circe-ExtraBold.woff

1469 ms

Cambria-Bold.woff

Cambria-Bold.woff

1730 ms

calculatorsv4.jpg

calculatorsv4.jpg

2222 ms

calculatoricon.png

calculatoricon.png

1624 ms

testimonials.jpg

testimonials.jpg

1637 ms

video.php

video.php

52 ms

footerbg.jpg

footerbg.jpg

1639 ms

video.php

video.php

285 ms

recaptcha__en.js

recaptcha__en.js

82 ms

cbp-loading.gif

cbp-loading.gif

1670 ms

rate-it-icons.png

rate-it-icons.png

1683 ms

-dY0pTbksYU.css

-dY0pTbksYU.css

27 ms

PsN7z1yfDJ7.js

PsN7z1yfDJ7.js

75 ms

vmUY4WOjQVQ.js

vmUY4WOjQVQ.js

98 ms

6xyFvE08ZOF.js

6xyFvE08ZOF.js

103 ms

4r8pcxnOs4K.js

4r8pcxnOs4K.js

101 ms

YOEXhEYeCQr.js

YOEXhEYeCQr.js

102 ms

xJP_bJvoKXI.js

xJP_bJvoKXI.js

101 ms

KeKWJi20nnK.js

KeKWJi20nnK.js

100 ms

0oPeSI6u9hD.js

0oPeSI6u9hD.js

100 ms

EAH61G-v2VL.js

EAH61G-v2VL.js

123 ms

1IebFaTaEsE.js

1IebFaTaEsE.js

102 ms

71748740_2551544645097493_9208115655360880933_n.jpg

71748740_2551544645097493_9208115655360880933_n.jpg

41 ms

438275488_1149557366411649_4383315312969945149_n.jpg

438275488_1149557366411649_4383315312969945149_n.jpg

40 ms

PbZ9XhPJHr4.js

PbZ9XhPJHr4.js

16 ms

iTmVIlBRgPP.png

iTmVIlBRgPP.png

15 ms

vwOUmvzU_7P.png

vwOUmvzU_7P.png

14 ms

Accessibility Review

yorkestone.co.nz accessibility score

77

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

Image elements do not have [alt] attributes

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

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

yorkestone.co.nz best practices score

75

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

yorkestone.co.nz SEO score

92

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

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

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

yorkestone.co.nz

Open Graph description is not detected on the main page of Yorke Stone. 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: