Tools & Wizards About Us
nclr.org.nz screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

nclr.org.nz

National Centre For Lifecourse Research Home, National Centre For Lifecourse Research, University of Otago, New Zealand

Page Load Speed

7.6 sec in total

First Response

476 ms

Resources Loaded

7 sec

Page Rendered

164 ms

nclr.org.nz screenshot

About Website

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

The National Centre for Lifecourse Research (NCLR) and its partners undertake world-leading lifecourse research, with a focus on studies that impact on policy and practice. The NCLR is a part of the D...

Visit nclr.org.nz

Key Findings

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

Performance Metrics

nclr.org.nz performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value920 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value8.8 s

35/100

10%

Network Requests Diagram

nclr

476 ms

nclr

905 ms

index.html

637 ms

sitenavigationfunctions.js

238 ms

sitenavigation.js

465 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Nclr.org.nz, 7% (5 requests) were made to Cdnjs.cloudflare.com and 6% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Otago.ac.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 64.4 kB (14%)

Content Size

448.3 kB

After Optimization

384.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 20.2 kB

  • Original 26.6 kB
  • After minification 22.4 kB
  • After compression 6.5 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 4.2 kB, which is 16% 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 20.2 kB or 76% of the original size.

Image Optimization

-10%

Potential reduce by 32.9 kB

  • Original 344.3 kB
  • After minification 311.4 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. Nclr images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 4.1 kB

  • Original 38.7 kB
  • After minification 38.7 kB
  • After compression 34.5 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 4.1 kB or 11% of the original size.

CSS Optimization

-18%

Potential reduce by 7.1 kB

  • Original 38.7 kB
  • After minification 38.7 kB
  • After compression 31.6 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. Nclr.org.nz needs all CSS files to be minified and compressed as it can save up to 7.1 kB or 18% of the original size.

Requests Breakdown

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

Requests Now

67

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nclr

nclr

476 ms

nclr

nclr

905 ms

index.html

index.html

637 ms

sitenavigationfunctions.js

sitenavigationfunctions.js

238 ms

sitenavigation.js

sitenavigation.js

465 ms

wcm.toggle.js

wcm.toggle.js

696 ms

ssajax.js

ssajax.js

695 ms

global.css

global.css

1568 ms

jquery-ui.min.css

jquery-ui.min.css

171 ms

mobile_navigation.css

mobile_navigation.css

935 ms

nclr.css

nclr.css

694 ms

jquery.min.js

jquery.min.js

207 ms

jquery-migrate.min.js

jquery-migrate.min.js

208 ms

modernizr.min.js

modernizr.min.js

192 ms

jquery-ui.min.js

jquery-ui.min.js

236 ms

general.min.js

general.min.js

692 ms

navigation_slider_and_flyouts.min.js

navigation_slider_and_flyouts.min.js

933 ms

mobile_navigation.min.js

mobile_navigation.min.js

932 ms

translate_footer.min.js

translate_footer.min.js

931 ms

gtm.js

gtm.js

120 ms

css

css

86 ms

analytics.js

analytics.js

68 ms

js

js

107 ms

linkid.js

linkid.js

31 ms

collect

collect

68 ms

collect

collect

73 ms

collect

collect

31 ms

collect

collect

44 ms

ga-audiences

ga-audiences

60 ms

emergency-icon.svg

emergency-icon.svg

280 ms

sprite-nav.png

sprite-nav.png

282 ms

logo.png

logo.png

282 ms

flyout_right_background.png

flyout_right_background.png

283 ms

site-border-bg.png

site-border-bg.png

278 ms

sprite-search.png

sprite-search.png

283 ms

banner-frontpage.jpg

banner-frontpage.jpg

651 ms

title.png

title.png

493 ms

otago732746.jpg

otago732746.jpg

494 ms

otago834762.jpg

otago834762.jpg

877 ms

otago738054.jpg

otago738054.jpg

496 ms

otago330208.jpg

otago330208.jpg

1327 ms

bg-footer.png

bg-footer.png

657 ms

bg-footer-li.png

bg-footer-li.png

663 ms

translate-icon.png

translate-icon.png

663 ms

bg-footer-totop.png

bg-footer-totop.png

870 ms

kowhaiwhai-head.png

kowhaiwhai-head.png

875 ms

mnu-logo-grey-frontpage.png

mnu-logo-grey-frontpage.png

879 ms

qs-stars-grey-logo-2021.png

qs-stars-grey-logo-2021.png

858 ms

bg-htag-1px-grey.png

bg-htag-1px-grey.png

1074 ms

bg-footer-social-media.png

bg-footer-social-media.png

1083 ms

sprite-socialmedia-icons.png

sprite-socialmedia-icons.png

1074 ms

bg-footer-li-2.png

bg-footer-li-2.png

1085 ms

56gpq7sxl7

56gpq7sxl7

249 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

207 ms

clarity.js

clarity.js

100 ms

icon-home.svg

icon-home.svg

717 ms

search-icon-mobile.svg

search-icon-mobile.svg

920 ms

cdf_flyout_thinking.xml

cdf_flyout_thinking.xml

871 ms

cdf_flyout_students.xml

cdf_flyout_students.xml

895 ms

cdf_flyout_staff.xml

cdf_flyout_staff.xml

881 ms

cdf_flyout_about.xml

cdf_flyout_about.xml

891 ms

cdf_flyout_research.xml

cdf_flyout_research.xml

1083 ms

cdf_flyout_learning.xml

cdf_flyout_learning.xml

1085 ms

cdf_flyout_maori.xml

cdf_flyout_maori.xml

1076 ms

cdf_flyout_international.xml

cdf_flyout_international.xml

1077 ms

cdf_flyout_alumni.xml

cdf_flyout_alumni.xml

1077 ms

cdf_flyout_contact.xml

cdf_flyout_contact.xml

1064 ms

cdf_flyout_pacific.xml

cdf_flyout_pacific.xml

1265 ms

bookmark-menu.svg

bookmark-menu.svg

1216 ms

print.css

print.css

219 ms

c.gif

c.gif

53 ms

Accessibility Review

nclr.org.nz accessibility score

100

Accessibility Issues

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

nclr.org.nz SEO score

83

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

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

nclr.org.nz

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