Tools & Wizards About Us
rsea.co.nz screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

rsea.co.nz

RSEA Safety NZ - New Zealand's Workwear and Equipment Safety Shop

Page Load Speed

3.8 sec in total

First Response

606 ms

Resources Loaded

3.1 sec

Page Rendered

62 ms

rsea.co.nz screenshot

About Website

Click here to check amazing RSEA content. Otherwise, check out these important facts you probably never knew about rsea.co.nz

Visit rsea.co.nz

Key Findings

We analyzed Rsea.co.nz page load time and found that the first response time was 606 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

rsea.co.nz performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value10.8 s

7/100

10%

TBT (Total Blocking Time)

Value3,660 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.057

98/100

15%

TTI (Time to Interactive)

Value15.6 s

7/100

10%

Network Requests Diagram

rsea.co.nz

606 ms

www.rsea.co.nz

79 ms

shopping_6.css

466 ms

shopping.environment.ssp

1791 ms

shopping.environment.shortcache.ssp

1938 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 86% of them (12 requests) were addressed to the original Rsea.co.nz, 14% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Rsea.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 693.5 kB (45%)

Content Size

1.5 MB

After Optimization

839.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Rsea.co.nz main page is 1.5 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. 15% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 3.8 kB

  • Original 5.9 kB
  • After minification 5.5 kB
  • After compression 2.1 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 3.8 kB or 64% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 282.9 kB
  • After minification 282.9 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. RSEA images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 689.7 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 554.8 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 689.7 kB or 55% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (42%)

Requests Now

12

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rsea.co.nz

rsea.co.nz

606 ms

www.rsea.co.nz

www.rsea.co.nz

79 ms

shopping_6.css

shopping_6.css

466 ms

shopping.environment.ssp

shopping.environment.ssp

1791 ms

shopping.environment.shortcache.ssp

shopping.environment.shortcache.ssp

1938 ms

shopping_en_US.js

shopping_en_US.js

493 ms

shopping-templates_6.js

shopping-templates_6.js

500 ms

shopping.js

shopping.js

587 ms

shopping_6.js

shopping_6.js

1376 ms

cms-templates

cms-templates

1520 ms

css

css

48 ms

css

css

60 ms

ShoppingUserEnvironment.Service.ss

ShoppingUserEnvironment.Service.ss

1267 ms

home-ex-img-03.jpg

home-ex-img-03.jpg

66 ms

Accessibility Review

rsea.co.nz accessibility score

57

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-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

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

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

rsea.co.nz SEO score

82

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

rsea.co.nz

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