11.4 sec in total
776 ms
10.5 sec
114 ms
Click here to check amazing Webmail Uwa content for Australia. Otherwise, check out these important facts you probably never knew about webmail.uwa.edu.au
Links to webmail for staff and students at the University of Western Australia
Visit webmail.uwa.edu.auWe analyzed Webmail.uwa.edu.au page load time and found that the first response time was 776 ms and then it took 10.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
webmail.uwa.edu.au performance score
name
value
score
weighting
Value12.5 s
0/100
10%
Value13.6 s
0/100
25%
Value16.2 s
0/100
10%
Value210 ms
88/100
30%
Value0.099
90/100
15%
Value13.0 s
12/100
10%
776 ms
940 ms
784 ms
2848 ms
2031 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Webmail.uwa.edu.au, 74% (45 requests) were made to Static.weboffice.uwa.edu.au and 8% (5 requests) were made to Uwa.edu.au. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Web.uwa.edu.au.
Page size can be reduced by 231.7 kB (42%)
545.3 kB
313.7 kB
In fact, the total size of Webmail.uwa.edu.au main page is 545.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. 25% of websites need less resources to load. Images take 257.6 kB which makes up the majority of the site volume.
Potential reduce by 18.0 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 5.2 kB, which is 23% 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 18.0 kB or 80% of the original size.
Potential reduce by 5.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. Webmail Uwa images are well optimized though.
Potential reduce by 72.6 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 72.6 kB or 68% of the original size.
Potential reduce by 135.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. Webmail.uwa.edu.au needs all CSS files to be minified and compressed as it can save up to 135.8 kB or 86% of the original size.
Number of requests can be reduced by 41 (76%)
54
13
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Webmail 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 8 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
webmail.uwa.edu.au
776 ms
webmail
940 ms
webmail
784 ms
webmail
2848 ms
id-core.css
2031 ms
id-responsive.css
1269 ms
id-core.js
1776 ms
id-responsive.js
2040 ms
id-css-devices.php
1272 ms
id-css-layouts.php
1272 ms
id-js-devices.php
1526 ms
testimonial_dl.css
1523 ms
graduate_profiles.css
1524 ms
mings-landing-3-col-layout.css
1778 ms
studentnet_definition_lists.css
1779 ms
id-cat.php
2544 ms
colorbox.css
2040 ms
core5rebrand-inlinetest.js
1795 ms
uwa.css
259 ms
id-analytics-universal.js
1795 ms
webtrends.js
1779 ms
uwa.css
1822 ms
analytics.js
24 ms
www.uwa.edu.au
1253 ms
stamp-UNIFI.jpg
266 ms
button-cyllene.jpg
264 ms
staff-button-photo.jpg
769 ms
shadow_integrated.png
263 ms
search-background.gif
263 ms
ql_rightbottom.gif
261 ms
uwacrest-print.gif
513 ms
uwacrest.gif
257 ms
ql_leftbottom.gif
263 ms
bullet-default.gif
512 ms
ql_reticle.gif
518 ms
search-button-go.gif
515 ms
nav-arrow.gif
515 ms
bullet-discrete.gif
517 ms
page-banner-dotoverlay.gif
767 ms
dots-lightgrey.gif
769 ms
bevel-top-flow.gif
769 ms
bevel-right-flow.gif
770 ms
bevel-bottom-flow.gif
772 ms
bevel-left-flow.gif
771 ms
bevel-flow.gif
1021 ms
bevel-corners.png
1024 ms
footer-background.gif
1023 ms
footer-watermark.gif
1026 ms
footer-infoarrow.gif
1024 ms
id-brand-refresh-hack.css
1019 ms
jquery.js
13 ms
uwacrest.png
1267 ms
collect
8 ms
collect
62 ms
ga-audiences
40 ms
stamp-UNIFI.jpg
259 ms
header-refresh-background.jpg
1280 ms
id-nonvisual.css
258 ms
id-print.css
258 ms
uwa-responsive.css
259 ms
uwa-responsive-newcore.css
258 ms
webmail.uwa.edu.au accessibility score
webmail.uwa.edu.au best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
webmail.uwa.edu.au 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 Webmail.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 Webmail.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.
webmail.uwa.edu.au
Open Graph description is not detected on the main page of Webmail 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: