7 sec in total
1.2 sec
5.6 sec
171 ms
Click here to check amazing Voyager Auckland content for New Zealand. Otherwise, check out these important facts you probably never knew about voyager.auckland.ac.nz
Visit voyager.auckland.ac.nzWe analyzed Voyager.auckland.ac.nz page load time and found that the first response time was 1.2 sec and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
voyager.auckland.ac.nz performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value6.1 s
12/100
25%
Value10.6 s
7/100
10%
Value10 ms
100/100
30%
Value0.003
100/100
15%
Value6.1 s
63/100
10%
1197 ms
1277 ms
402 ms
382 ms
1154 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Voyager.auckland.ac.nz, 55% (22 requests) were made to Librarysearch.auckland.ac.nz and 35% (14 requests) were made to Library.auckland.ac.nz. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Pds4.its.auckland.ac.nz.
Page size can be reduced by 253.5 kB (73%)
348.1 kB
94.6 kB
In fact, the total size of Voyager.auckland.ac.nz main page is 348.1 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 185.0 kB which makes up the majority of the site volume.
Potential reduce by 39.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 9.5 kB, which is 19% 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 39.1 kB or 80% of the original size.
Potential reduce by 137.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. Obviously, Voyager Auckland needs image optimization as it can save up to 137.2 kB or 74% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 70.3 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 70.3 kB or 68% of the original size.
Potential reduce by 6.9 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. Voyager.auckland.ac.nz needs all CSS files to be minified and compressed as it can save up to 6.9 kB or 66% of the original size.
Number of requests can be reduced by 24 (67%)
36
12
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Voyager Auckland. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
voyager.auckland.ac.nz
1197 ms
search.do
1277 ms
primo_library_wro_UOA2_A_en_US.css
402 ms
primo_library_wro_UOA2_A_en_US.js
382 ms
primo_library_web.js
1154 ms
add2home.js
384 ms
add2home.css
384 ms
admin001a.js
985 ms
banner.css
983 ms
ez_proxy.js
989 ms
primo_general.js
990 ms
primo_popups.js
995 ms
primo_searchHelp.js
992 ms
primo_signin.js
995 ms
primo_watermark.js
1001 ms
primo_combined_1.js
1219 ms
primo_messages.js
1220 ms
pleaseWait.js
385 ms
banner.css
241 ms
admin001a.js
398 ms
analytics.js
6 ms
logo.png
197 ms
banner.png
193 ms
bs-background-2.jpg
390 ms
bs-logo.png
388 ms
empty.png
198 ms
icon_star_on.png
194 ms
bg_strip_searchPanel.png
193 ms
bg_strip_search_tabs.png
190 ms
icon_clear_search.png
361 ms
bg_strip_btn_orange.png
365 ms
Xhome_main_visual.jpg
378 ms
Xbullet_arrow_orange.png
375 ms
bg_banner_home_iPhone.png
385 ms
bg_strip_home_banners.png
381 ms
icon_newbook_rss_orange.png
550 ms
bg_strip_footer.png
551 ms
icon_sso_loading.gif
544 ms
pds
1539 ms
PDSMExlibris.css
190 ms
voyager.auckland.ac.nz accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
voyager.auckland.ac.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
voyager.auckland.ac.nz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Voyager.auckland.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 Voyager.auckland.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.
voyager.auckland.ac.nz
Open Graph description is not detected on the main page of Voyager Auckland. 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: