Tools & Wizards About Us
nzsti.org screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

nzsti.org

New Zealand Society of Translators & Interpreters | NZSTI

Page Load Speed

5.5 sec in total

First Response

658 ms

Resources Loaded

4.5 sec

Page Rendered

347 ms

nzsti.org screenshot

About Website

Visit nzsti.org now to see the best up-to-date NZSTI content for New Zealand and also check out these interesting facts you probably never knew about nzsti.org

NZSTI is the national professional association for translators and interpreters offering their member services to government agencies and the wider community.

Visit nzsti.org

Key Findings

We analyzed Nzsti.org page load time and found that the first response time was 658 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

nzsti.org performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.253

49/100

15%

TTI (Time to Interactive)

Value7.7 s

45/100

10%

Network Requests Diagram

nzsti.org

658 ms

nzsti.org

1535 ms

master

383 ms

css

28 ms

css

45 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 82% of them (36 requests) were addressed to the original Nzsti.org, 7% (3 requests) were made to Fonts.googleapis.com and 7% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Nzsti.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 403.0 kB (17%)

Content Size

2.4 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nzsti.org main page is 2.4 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. 50% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 58.5 kB

  • Original 81.1 kB
  • After minification 77.1 kB
  • After compression 22.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. 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 58.5 kB or 72% of the original size.

Image Optimization

-14%

Potential reduce by 288.5 kB

  • Original 2.1 MB
  • After minification 1.8 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. Obviously, NZSTI needs image optimization as it can save up to 288.5 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-26%

Potential reduce by 56.0 kB

  • Original 215.1 kB
  • After minification 215.1 kB
  • After compression 159.1 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 56.0 kB or 26% of the original size.

CSS Optimization

-2%

Potential reduce by 70 B

  • Original 4.2 kB
  • After minification 4.2 kB
  • After compression 4.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. Nzsti.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 8 (21%)

Requests Now

39

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nzsti.org

nzsti.org

658 ms

nzsti.org

nzsti.org

1535 ms

master

master

383 ms

css

css

28 ms

css

css

45 ms

icon

icon

54 ms

master

master

579 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

761 ms

WebResource.axd

WebResource.axd

753 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

1368 ms

masterjq

masterjq

591 ms

gtm.js

gtm.js

55 ms

logo_main.svg

logo_main.svg

374 ms

button_join.svg

button_join.svg

190 ms

home_people_01.jpg

home_people_01.jpg

564 ms

home_people_02.jpg

home_people_02.jpg

560 ms

home_people_03.jpg

home_people_03.jpg

569 ms

home_people_04.jpg

home_people_04.jpg

758 ms

home_people_05.jpg

home_people_05.jpg

751 ms

home_people_06.jpg

home_people_06.jpg

935 ms

icon_translator_lge.svg

icon_translator_lge.svg

753 ms

icon_interpreter_lge.svg

icon_interpreter_lge.svg

759 ms

NZSTI%20conference%20logo.png

NZSTI%20conference%20logo.png

793 ms

question%20mark.png

question%20mark.png

1125 ms

project_home_01.jpg

project_home_01.jpg

1130 ms

word%204word.PNG

word%204word.PNG

949 ms

noimage_sml.jpg

noimage_sml.jpg

949 ms

b3febaca-7ff6-42de-84b3-f2316eee7ea5.jpg

b3febaca-7ff6-42de-84b3-f2316eee7ea5.jpg

983 ms

a0fa19fb-cb70-4321-9585-4cf86068fa1f.png

a0fa19fb-cb70-4321-9585-4cf86068fa1f.png

1310 ms

41019bde-9135-4f1a-b867-1e1196257636.jpg

41019bde-9135-4f1a-b867-1e1196257636.jpg

1138 ms

be58693f-a652-4531-91df-fd261a31123a.jpg

be58693f-a652-4531-91df-fd261a31123a.jpg

1139 ms

E584092D-C0FF-411B-9B50-7D58BBBE5A6F.png

E584092D-C0FF-411B-9B50-7D58BBBE5A6F.png

1171 ms

icon_fb_40_40_white.svg

icon_fb_40_40_white.svg

1312 ms

icon_twitter_40_40_white.svg

icon_twitter_40_40_white.svg

1317 ms

logo_ft_streamsweet_color.svg

logo_ft_streamsweet_color.svg

1329 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

15 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

19 ms

button_find_interpreter.svg

button_find_interpreter.svg

681 ms

button_find_translator.svg

button_find_translator.svg

709 ms

button_find_interpreter_sml.svg

button_find_interpreter_sml.svg

847 ms

button_find_translator_sml.svg

button_find_translator_sml.svg

848 ms

home_search_feature.jpg

home_search_feature.jpg

857 ms

flUhRq6tzZclQEJ-Vdg-IuiaDsNZ.ttf

flUhRq6tzZclQEJ-Vdg-IuiaDsNZ.ttf

16 ms

Tracker.aspx

Tracker.aspx

1083 ms

Accessibility Review

nzsti.org accessibility score

81

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

Best Practices

nzsti.org best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

nzsti.org SEO score

75

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 Nzsti.org 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 Nzsti.org 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

nzsti.org

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