7.3 sec in total
1.1 sec
6 sec
225 ms
Visit research-repository.uwa.edu.au now to see the best up-to-date Research Repository UWA content for Australia and also check out these interesting facts you probably never knew about research-repository.uwa.edu.au
Visit research-repository.uwa.edu.auWe analyzed Research-repository.uwa.edu.au page load time and found that the first response time was 1.1 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
research-repository.uwa.edu.au performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value5.7 s
16/100
25%
Value9.8 s
10/100
10%
Value350 ms
73/100
30%
Value0.143
78/100
15%
Value9.7 s
29/100
10%
1084 ms
1532 ms
769 ms
1278 ms
1537 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 31% of them (15 requests) were addressed to the original Research-repository.uwa.edu.au, 65% (31 requests) were made to Static.weboffice.uwa.edu.au and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Research-repository.uwa.edu.au.
Page size can be reduced by 520.5 kB (54%)
962.4 kB
441.9 kB
In fact, the total size of Research-repository.uwa.edu.au main page is 962.4 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. 25% of websites need less resources to load. Javascripts take 538.8 kB which makes up the majority of the site volume.
Potential reduce by 22.8 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 6.3 kB, which is 22% 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 22.8 kB or 81% of the original size.
Potential reduce by 11.9 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. Research Repository UWA images are well optimized though.
Potential reduce by 415.0 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 415.0 kB or 77% of the original size.
Potential reduce by 70.8 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. Research-repository.uwa.edu.au needs all CSS files to be minified and compressed as it can save up to 70.8 kB or 86% of the original size.
Number of requests can be reduced by 33 (70%)
47
14
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Research Repository UWA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
research-repository.uwa.edu.au
1084 ms
id-core.css
1532 ms
id-responsive.css
769 ms
id-core.js
1278 ms
id-responsive.js
1537 ms
id-css-devices.php
771 ms
id-css-layouts.php
772 ms
id-js-devices.php
1024 ms
portal.css
1028 ms
jquery.js
1280 ms
site.js
515 ms
engine.js
1024 ms
PureFacade.js
515 ms
prototype.js
2291 ms
atira.js
1556 ms
atira_chart.js
1555 ms
GraphFacade.js
1555 ms
portal.js
2049 ms
id-nonvisual.css
257 ms
id-print.css
259 ms
shadow_integrated.png
259 ms
uwa-research-portal.png
516 ms
research.jpg
772 ms
uwa-research-data-online.png
773 ms
open-access-toolkit.png
518 ms
search-background.gif
257 ms
ql_rightbottom.gif
257 ms
uwacrest-print.gif
766 ms
uwacrest.gif
259 ms
ql_leftbottom.gif
258 ms
bullet-default.gif
501 ms
ql_reticle.gif
513 ms
bullet-link.gif
511 ms
search-button-go.gif
515 ms
nav-arrow-current.gif
515 ms
nav-arrow.gif
757 ms
bullet-discrete.gif
768 ms
dots-lightgrey.gif
756 ms
footer-background.gif
757 ms
footer-watermark.gif
757 ms
analytics.js
29 ms
id-brand-refresh-hack.css
984 ms
uwacrest.png
970 ms
collect
25 ms
header-refresh-background.jpg
1535 ms
uwa-slab-regular.otf
256 ms
uwa-responsive.css
259 ms
uwa-responsive-newcore.css
259 ms
research-repository.uwa.edu.au accessibility score
research-repository.uwa.edu.au 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
research-repository.uwa.edu.au SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 Research-repository.uwa.edu.au 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 Research-repository.uwa.edu.au 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.
research-repository.uwa.edu.au
Open Graph description is not detected on the main page of Research Repository UWA. 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: