2.9 sec in total
116 ms
2.6 sec
221 ms
Click here to check amazing UW Arboretum content for United States. Otherwise, check out these important facts you probably never knew about uwarboretum.org
Visit uwarboretum.orgWe analyzed Uwarboretum.org page load time and found that the first response time was 116 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
uwarboretum.org performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value6.5 s
9/100
25%
Value5.3 s
57/100
10%
Value20 ms
100/100
30%
Value0
100/100
15%
Value4.0 s
87/100
10%
116 ms
1817 ms
54 ms
115 ms
140 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 Uwarboretum.org, 80% (32 requests) were made to Arboretum.wisc.edu and 8% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Arboretum.wisc.edu.
Page size can be reduced by 267.3 kB (31%)
855.1 kB
587.8 kB
In fact, the total size of Uwarboretum.org main page is 855.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. 35% of websites need less resources to load. Images take 498.1 kB which makes up the majority of the site volume.
Potential reduce by 22.2 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 4.6 kB, which is 16% 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.2 kB or 79% of the original size.
Potential reduce by 15.5 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. UW Arboretum images are well optimized though.
Potential reduce by 180.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 180.6 kB or 68% of the original size.
Potential reduce by 49.0 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. Uwarboretum.org needs all CSS files to be minified and compressed as it can save up to 49.0 kB or 79% of the original size.
Number of requests can be reduced by 12 (34%)
35
23
The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of UW Arboretum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
uwarboretum.org
116 ms
arboretum.wisc.edu
1817 ms
css
54 ms
arboretum.min.css
115 ms
photoswipe.css
140 ms
default-skin.css
152 ms
jquery.js
304 ms
jquery-migrate.min.js
146 ms
site.js
110 ms
photoswipe.js
363 ms
photoswipe-ui-default.min.js
120 ms
galleries.js
128 ms
homepage-slider.js
152 ms
wp-embed.min.js
174 ms
wp-emoji-release.min.js
111 ms
analytics.js
28 ms
collect
4 ms
collect
52 ms
bannerBg.gif
189 ms
crest2.png
194 ms
search.png
188 ms
navBg.png
189 ms
navDivider.png
189 ms
FEAwin_robin-crabapple_3509SD-165x100.jpg
190 ms
FEAwin131204_LHG-fog_6286SD-165x100.jpg
191 ms
FEAwin_131219_ice-prairie_3723SD-165x100.jpg
192 ms
FEAwin_140204_wetlands-snowy_7086SD-528x320.jpg
195 ms
col3Tours.png
193 ms
col3Give.png
192 ms
col3Friends.png
191 ms
WSJ_MP-King_Jackson-Oak.jpg
329 ms
Pollinators_B-impatiens-goldenrod_SGC0109-294x105-c-default.jpg
196 ms
Spr-blooms_MagnoliaMFMDSC_0386_album-294x105-c-default.jpg
192 ms
sm_fb.png
193 ms
sm_twitter.png
194 ms
sm_instagram.png
195 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
25 ms
toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf
29 ms
toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf
41 ms
friz.woff
42 ms
uwarboretum.org accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
uwarboretum.org 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
uwarboretum.org SEO score
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 Uwarboretum.org 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 Uwarboretum.org 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.
uwarboretum.org
Open Graph description is not detected on the main page of UW Arboretum. 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: