Tools & Wizards About Us
cpr.otago.ac.nz screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

cpr.otago.ac.nz

Centre for Protein Research Home, Centre for Protein Research | University of Otago

Page Load Speed

5.6 sec in total

First Response

445 ms

Resources Loaded

5 sec

Page Rendered

231 ms

cpr.otago.ac.nz screenshot

About Website

Click here to check amazing Cpr Otago content for New Zealand. Otherwise, check out these important facts you probably never knew about cpr.otago.ac.nz

The Centre for Protein Research (CPR) is a research facility for biological mass spectrometry. We offer a service facility and a user laboratory that supports research and student projects within the ...

Visit cpr.otago.ac.nz

Key Findings

We analyzed Cpr.otago.ac.nz page load time and found that the first response time was 445 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

cpr.otago.ac.nz performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value3,190 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.131

81/100

15%

TTI (Time to Interactive)

Value26.5 s

0/100

10%

Network Requests Diagram

cpr.otago.ac.nz

445 ms

protein

1744 ms

main.css

1393 ms

widget.js

172 ms

main.js

1296 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Cpr.otago.ac.nz, 58% (15 requests) were made to Otago.ac.nz and 12% (3 requests) were made to Cdn.userway.org. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Otago.ac.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 355.7 kB (13%)

Content Size

2.8 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cpr.otago.ac.nz main page is 2.8 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. 40% of websites need less resources to load. Javascripts take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-57%

Potential reduce by 343.6 kB

  • Original 607.7 kB
  • After minification 527.4 kB
  • After compression 264.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. This page needs HTML code to be minified as it can gain 80.3 kB, which is 13% 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 343.6 kB or 57% of the original size.

Image Optimization

-3%

Potential reduce by 11.3 kB

  • Original 326.6 kB
  • After minification 315.2 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. Cpr Otago images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 706 B

  • Original 1.8 MB
  • After minification 1.8 MB
  • After compression 1.8 MB

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

-0%

Potential reduce by 0 B

  • Original 105.1 kB
  • After minification 105.1 kB
  • After compression 105.1 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. Cpr.otago.ac.nz has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 7 (35%)

Requests Now

20

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cpr.otago.ac.nz

cpr.otago.ac.nz

445 ms

protein

protein

1744 ms

main.css

main.css

1393 ms

widget.js

widget.js

172 ms

main.js

main.js

1296 ms

htmx.min.js

htmx.min.js

795 ms

_Incapsula_Resource

_Incapsula_Resource

435 ms

css2

css2

45 ms

gtm.js

gtm.js

142 ms

56gpq7sxl7

56gpq7sxl7

129 ms

UoO_Logo_RGB_Horz_Gold-REV.svg

UoO_Logo_RGB_Horz_Gold-REV.svg

465 ms

protein-banner.jpg

protein-banner.jpg

1004 ms

cpr-entry-662291.jpg

cpr-entry-662291.jpg

1693 ms

1869-emblem.png

1869-emblem.png

639 ms

matariki-logo-white.png

matariki-logo-white.png

817 ms

QS-Logo.png

QS-Logo.png

838 ms

WickliffeSansWEB-Medium..woff

WickliffeSansWEB-Medium..woff

1200 ms

WickliffeSansWEB-Regular..woff

WickliffeSansWEB-Regular..woff

1382 ms

WickliffeWEB-Regular..woff

WickliffeWEB-Regular..woff

1207 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObjz2VZyOOSr4dVJWUgsjZ0C4nY1M2xYkS.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObjz2VZyOOSr4dVJWUgsjZ0C4nY1M2xYkS.ttf

49 ms

clarity.js

clarity.js

29 ms

widget_app_base_1724849559553.js

widget_app_base_1724849559553.js

36 ms

_Incapsula_Resource

_Incapsula_Resource

79 ms

aUa3lcVWRi

aUa3lcVWRi

383 ms

en-US.json

en-US.json

7 ms

c.gif

c.gif

8 ms

Accessibility Review

cpr.otago.ac.nz accessibility score

89

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Heading elements are not in a sequentially-descending order

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 IDs are not unique

Best Practices

cpr.otago.ac.nz best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

cpr.otago.ac.nz SEO score

100

Search Engine Optimization Advices

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 Cpr.otago.ac.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 Cpr.otago.ac.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

cpr.otago.ac.nz

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