Tools & Wizards About Us
proto.co.nz screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

proto.co.nz

Proto Electronics – Scoreboards, LED Displays & Signage Solutions

Page Load Speed

14.1 sec in total

First Response

2.1 sec

Resources Loaded

10.9 sec

Page Rendered

1.1 sec

proto.co.nz screenshot

About Website

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

Visit proto.co.nz

Key Findings

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

Performance Metrics

proto.co.nz performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value28.0 s

0/100

25%

SI (Speed Index)

Value19.8 s

0/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.171

70/100

15%

TTI (Time to Interactive)

Value21.3 s

1/100

10%

Network Requests Diagram

proto.co.nz

2052 ms

global.css

860 ms

frontend_blocks.css

1076 ms

frontend_blocks_responsive.css

650 ms

main.css

648 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 71% of them (69 requests) were addressed to the original Proto.co.nz, 18% (17 requests) were made to Static.xx.fbcdn.net and 6% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Facebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 710.3 kB (9%)

Content Size

8.2 MB

After Optimization

7.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Proto.co.nz main page is 8.2 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 7.3 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 132.0 kB

  • Original 155.9 kB
  • After minification 154.5 kB
  • After compression 23.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 132.0 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 726 B

  • Original 7.3 MB
  • After minification 7.3 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. Proto images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 279.5 kB

  • Original 405.9 kB
  • After minification 399.4 kB
  • After compression 126.3 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 279.5 kB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 298.1 kB

  • Original 357.5 kB
  • After minification 355.3 kB
  • After compression 59.5 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. Proto.co.nz needs all CSS files to be minified and compressed as it can save up to 298.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 49 (54%)

Requests Now

90

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

proto.co.nz

proto.co.nz

2052 ms

global.css

global.css

860 ms

frontend_blocks.css

frontend_blocks.css

1076 ms

frontend_blocks_responsive.css

frontend_blocks_responsive.css

650 ms

main.css

main.css

648 ms

swiper-bundle.min.css

swiper-bundle.min.css

864 ms

layout-slider.css

layout-slider.css

873 ms

simplebar.min.css

simplebar.min.css

870 ms

custom-scrollbar.css

custom-scrollbar.css

1069 ms

lazyload.css

lazyload.css

1076 ms

style.css

style.css

1081 ms

style.css

style.css

1084 ms

style.css

style.css

1087 ms

style.min.css

style.min.css

1505 ms

blocks.style.build.css

blocks.style.build.css

1292 ms

css2

css2

27 ms

main.min.css

main.min.css

1510 ms

stackable.min.css

stackable.min.css

1088 ms

wpforms.min.css

wpforms.min.css

1088 ms

jquery.min.js

jquery.min.js

1520 ms

jquery-migrate.min.js

jquery-migrate.min.js

1303 ms

css

css

18 ms

modal.js

modal.js

666 ms

main.js

main.js

879 ms

frontend_block_video_popup.js

frontend_block_video_popup.js

879 ms

simplebar.min.js

simplebar.min.js

1101 ms

custom-scrollbar.js

custom-scrollbar.js

1000 ms

swiper-bundle.min.js

swiper-bundle.min.js

1303 ms

plugin-swiper.js

plugin-swiper.js

1100 ms

layout-slider.js

layout-slider.js

1099 ms

lazysizes-cfg.js

lazysizes-cfg.js

1100 ms

lazysizes-object-fit-cover.js

lazysizes-object-fit-cover.js

1110 ms

lazysizes-swiper-duplicates-load.js

lazysizes-swiper-duplicates-load.js

1312 ms

lazysizes.min.js

lazysizes.min.js

1316 ms

lazyload.js

lazyload.js

1317 ms

imagesloaded.min.js

imagesloaded.min.js

1315 ms

main.js

main.js

1327 ms

video.php

video.php

2830 ms

proto-logo.png

proto-logo.png

568 ms

proto-electronics.jpeg

proto-electronics.jpeg

766 ms

logo-dark.svg

logo-dark.svg

556 ms

rugby-sldr-1920x960.jpg

rugby-sldr-1920x960.jpg

776 ms

Proto-sldr-1920x960.jpg

Proto-sldr-1920x960.jpg

1005 ms

NHhockey-sldr-1920x960.jpg

NHhockey-sldr-1920x960.jpg

1709 ms

mediumBB.jpg

mediumBB.jpg

779 ms

medium-BB-showing-graphics.jpg

medium-BB-showing-graphics.jpg

784 ms

HVSotball-sldr.jpg

HVSotball-sldr.jpg

1198 ms

Hutt-City-sldr-1920x960.jpg

Hutt-City-sldr-1920x960.jpg

1012 ms

horse-polo-sldr.jpg

horse-polo-sldr.jpg

997 ms

hockey-sldr-1920x960.jpg

hockey-sldr-1920x960.jpg

1229 ms

cricket-sldr.jpg

cricket-sldr.jpg

1433 ms

CP-site-sldr.jpg

CP-site-sldr.jpg

1246 ms

Canoe-Polo-sldr.jpg

Canoe-Polo-sldr.jpg

1261 ms

Ballance-sldr-1920x960.jpg

Ballance-sldr-1920x960.jpg

1653 ms

basketball-sldr.jpg

basketball-sldr.jpg

1466 ms

blenheim-stadium-sldr-1920x960.jpg

blenheim-stadium-sldr-1920x960.jpg

1495 ms

bolws-timer-sldr.jpg

bolws-timer-sldr.jpg

1512 ms

bowls-SBs-sldr-1920x960.jpg

bowls-SBs-sldr-1920x960.jpg

1669 ms

Taupiri-cropped-1920x960.jpg

Taupiri-cropped-1920x960.jpg

1716 ms

waterpolo-cropped-1920x960.jpg

waterpolo-cropped-1920x960.jpg

1771 ms

whats-your-sport-basketball.jpg

whats-your-sport-basketball.jpg

1770 ms

whats-your-sport-rugby.png

whats-your-sport-rugby.png

2067 ms

6xK0dSxYI9_dkN18-vZKK2EISM2-L4nAkw.woff

6xK0dSxYI9_dkN18-vZKK2EISM2-L4nAkw.woff

17 ms

6xK0dSxYI9_dkN18-vZKK2EISM2-H40.woff

6xK0dSxYI9_dkN18-vZKK2EISM2-H40.woff

34 ms

6xK0dSxYI9_dkN18-vZKK2EISKq-L4nAkw.woff

6xK0dSxYI9_dkN18-vZKK2EISKq-L4nAkw.woff

56 ms

6xK0dSxYI9_dkN18-vZKK2EISPS-L4nAkw.woff

6xK0dSxYI9_dkN18-vZKK2EISPS-L4nAkw.woff

73 ms

6xK0dSxYI9_dkN18-vZKK2EISBi5L4nAkw.woff

6xK0dSxYI9_dkN18-vZKK2EISBi5L4nAkw.woff

127 ms

6xK0dSxYI9_dkN18-vZKK2EISCq5L4nAkw.woff

6xK0dSxYI9_dkN18-vZKK2EISCq5L4nAkw.woff

73 ms

whats-your-sport-hockey.png

whats-your-sport-hockey.png

2095 ms

whats-your-sport-WP.jpg

whats-your-sport-WP.jpg

1805 ms

hp-basketball-fiba2-scoreboard-proto.jpg

hp-basketball-fiba2-scoreboard-proto.jpg

1845 ms

scp-img-01-fiba-2-basketball-scoreboard.png

scp-img-01-fiba-2-basketball-scoreboard.png

1877 ms

scp-img-02-proto-electronics-countdown-clock.jpg

scp-img-02-proto-electronics-countdown-clock.jpg

1875 ms

proto-RTC-white-scaled.jpg

proto-RTC-white-scaled.jpg

2242 ms

Ballance-sldr-scaled.jpg

Ballance-sldr-scaled.jpg

1873 ms

video-bg.png

video-bg.png

2109 ms

hp-gal-proto-electronics-02.jpg

hp-gal-proto-electronics-02.jpg

1894 ms

nelson-bb-cropped-scaled.jpg

nelson-bb-cropped-scaled.jpg

1991 ms

6R_mYOSgyw5.css

6R_mYOSgyw5.css

13 ms

HpGlOE-g8mB.css

HpGlOE-g8mB.css

20 ms

_tdn2SGo1cv.js

_tdn2SGo1cv.js

63 ms

L-Ni4GtYemb.js

L-Ni4GtYemb.js

60 ms

G-C6uyILweu.js

G-C6uyILweu.js

60 ms

3F_uq95_jmA.js

3F_uq95_jmA.js

85 ms

BHcXcpC4qPw.js

BHcXcpC4qPw.js

60 ms

4r8pcxnOs4K.js

4r8pcxnOs4K.js

61 ms

dFXIXJelwR0.js

dFXIXJelwR0.js

93 ms

9g7aJrF47IZ.js

9g7aJrF47IZ.js

60 ms

MUc1r-cnaqL.js

MUc1r-cnaqL.js

83 ms

441968526_1169552604075000_4304389304163207485_n.jpg

441968526_1169552604075000_4304389304163207485_n.jpg

48 ms

325318264_1130917304283815_2735972908519782005_n.jpg

325318264_1130917304283815_2735972908519782005_n.jpg

55 ms

LIre8SWfHmj.js

LIre8SWfHmj.js

26 ms

DHqKGifLKMr.js

DHqKGifLKMr.js

8 ms

T_Psx53pBeu.js

T_Psx53pBeu.js

26 ms

PbZ9XhPJHr4.js

PbZ9XhPJHr4.js

8 ms

d8Rm2Jl_K6s.png

d8Rm2Jl_K6s.png

3 ms

vwOUmvzU_7P.png

vwOUmvzU_7P.png

6 ms

Accessibility Review

proto.co.nz accessibility score

91

Accessibility Issues

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

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

proto.co.nz best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

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

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

proto.co.nz

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