Tools & Wizards About Us

Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

nzdl.org

New Zealand Digital Library

Page Load Speed

10.9 sec in total

First Response

485 ms

Resources Loaded

10.1 sec

Page Rendered

346 ms

About Website

Click here to check amazing Nzdl content for India. Otherwise, check out these important facts you probably never knew about nzdl.org

Visit nzdl.org

Key Findings

We analyzed Nzdl.org page load time and found that the first response time was 485 ms and then it took 10.4 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

nzdl.org performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

81/100

25%

SI (Speed Index)

Value6.3 s

41/100

10%

TBT (Total Blocking Time)

Value210 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.411

24/100

15%

TTI (Time to Interactive)

Value4.9 s

78/100

10%

Network Requests Diagram

nzdl.org

485 ms

nzdl.org

687 ms

library.cgi

696 ms

style.css

684 ms

nzdl2gr.gif

681 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 97% of them (72 requests) were addressed to the original Nzdl.org, 3% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Nzdl.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 69.5 kB (44%)

Content Size

159.6 kB

After Optimization

90.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nzdl.org main page is 159.6 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. 30% of websites need less resources to load. Images take 107.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 25.4 kB

  • Original 32.1 kB
  • After minification 30.2 kB
  • After compression 6.7 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 25.4 kB or 79% of the original size.

Image Optimization

-40%

Potential reduce by 42.8 kB

  • Original 107.7 kB
  • After minification 65.0 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. Obviously, Nzdl needs image optimization as it can save up to 42.8 kB or 40% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.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. This website has mostly compressed JavaScripts.

CSS Optimization

-49%

Potential reduce by 1.3 kB

  • Original 2.7 kB
  • After minification 2.7 kB
  • After compression 1.4 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. Nzdl.org needs all CSS files to be minified and compressed as it can save up to 1.3 kB or 49% of the original size.

Requests Breakdown

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

Requests Now

71

After Optimization

65

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

nzdl.org accessibility score

63

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

nzdl.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

nzdl.org SEO score

54

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nzdl.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Nzdl.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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