8.5 sec in total
1.2 sec
7.3 sec
87 ms
Visit ezproxy.auckland.ac.nz now to see the best up-to-date Ezproxy Auckland content for New Zealand and also check out these interesting facts you probably never knew about ezproxy.auckland.ac.nz
Visit ezproxy.auckland.ac.nzWe analyzed Ezproxy.auckland.ac.nz page load time and found that the first response time was 1.2 sec and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ezproxy.auckland.ac.nz performance score
name
value
score
weighting
Value1.4 s
97/100
10%
Value5.6 s
17/100
25%
Value4.6 s
70/100
10%
Value40 ms
100/100
30%
Value0.013
100/100
15%
Value4.4 s
83/100
10%
1171 ms
391 ms
1392 ms
223 ms
195 ms
Our browser made a total of 23 requests to load all elements on the main page. We found that 9% of them (2 requests) were addressed to the original Ezproxy.auckland.ac.nz, 78% (18 requests) were made to Iam.auckland.ac.nz and 9% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Ezpappprd01.its.auckland.ac.nz.
Page size can be reduced by 401.8 kB (73%)
547.9 kB
146.1 kB
In fact, the total size of Ezproxy.auckland.ac.nz main page is 547.9 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. Only 10% of websites need less resources to load. Javascripts take 438.6 kB which makes up the majority of the site volume.
Potential reduce by 9.4 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 9.4 kB or 68% of the original size.
Potential reduce by 2.1 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. Ezproxy Auckland images are well optimized though.
Potential reduce by 332.9 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 332.9 kB or 76% of the original size.
Potential reduce by 57.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. Ezproxy.auckland.ac.nz needs all CSS files to be minified and compressed as it can save up to 57.4 kB or 80% of the original size.
Number of requests can be reduced by 3 (16%)
19
16
The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ezproxy 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 4 to 1 for JavaScripts and as a result speed up the page load time.
ezproxy.auckland.ac.nz
1171 ms
login
391 ms
ezpecad_sso.cgi
1392 ms
UserPassword
223 ms
bxujeodAMNbtUl7O6LJIhJEDLBBS7jHzZSb4muxJQQf.css
195 ms
1u8BcKWxzHq0pJFlQkOfNfNYca2USMoFgs3u0XF7deo.js
580 ms
9nNXyZCkl77SU59yrou6CBA73GENY4Vpw85Us6VGLYY.js
572 ms
vsRjSZylGQTuYIbud3V1jrXXkORNXakfFanicjYQUhg.css
760 ms
BM9v7dQegljKxNzFm5xi60QfwskIpB4XTx9nZDkLhGt.js
1324 ms
ga.js
56 ms
t8IqfVlSMpeEmlCddwy4Plt4AaT1M4AuAOQMQrjvmjp.png
193 ms
xAjGKewUiKrYrmS23HhNMoXi0919miKfa1ZqXlewj6k.png
193 ms
82Kppr4O6Jp7ncyFnC6PZfOINFnty6JFXTr1CNIincN.png
197 ms
7wjBIGzZfYiiBJ9LBDmme95ZVv9LqSFXfCSS35S9yto.jpg
195 ms
b8r1LVi2tpvK2RHKVMWlQxW54EmZoPEJllCmNwjtjh6.png
195 ms
qpOR1EDavja0l7LMI5dQasVuHO3Xx7VlfdzwxfnqqWd.gif
384 ms
T8SJo0YwtTi8KcXwB1ApRhF6Y8VVlazebd9CEYwHc1D.gif
569 ms
NtR6J0xjZtdQizCkhnxrx3jG84XezMXpwagRRPGPcLl.gif
386 ms
gOjs0ReCB2UOLJwsMPAQf0ndNYDWas3aEn3zdkiKyqe.png
370 ms
WrbTd6YetVvYhhDpl66C7PKkv5IIKNY1xygN6EyYuzA.png
372 ms
cV9L9emKSAK80rV6scWGXJ18Yo8WMQGHq88CsxrqqI.png
559 ms
__utm.gif
25 ms
0ZAdghkXmwXdR7OAl2bEmb5ZsJvqvenewpoL7DvYTI2.css
192 ms
ezproxy.auckland.ac.nz accessibility score
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
ezproxy.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
ezproxy.auckland.ac.nz SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Tap targets are not sized appropriately
N/A
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ezproxy.auckland.ac.nz can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Ezproxy.auckland.ac.nz main page’s claimed encoding is . 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.
ezproxy.auckland.ac.nz
Open Graph description is not detected on the main page of Ezproxy 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: