Tools & Wizards About Us
wam.leeds.ac.uk screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

wam.leeds.ac.uk

Leeds University Library Catalogue

Page Load Speed

1.7 sec in total

First Response

360 ms

Resources Loaded

1.2 sec

Page Rendered

144 ms

wam.leeds.ac.uk screenshot

About Website

Visit wam.leeds.ac.uk now to see the best up-to-date Wam Leeds content for United Kingdom and also check out these interesting facts you probably never knew about wam.leeds.ac.uk

Visit wam.leeds.ac.uk

Key Findings

We analyzed Wam.leeds.ac.uk page load time and found that the first response time was 360 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

wam.leeds.ac.uk performance score

0

Network Requests Diagram

wam.leeds.ac.uk

360 ms

ProStyles.css

102 ms

styles.css

264 ms

elcontent.js

179 ms

common.js

270 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 94% of them (29 requests) were addressed to the original Wam.leeds.ac.uk, 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (581 ms) belongs to the original domain Wam.leeds.ac.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 38.8 kB (62%)

Content Size

62.7 kB

After Optimization

23.8 kB

  • HTML
  • JavaScript

In fact, the total size of Wam.leeds.ac.uk main page is 62.7 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. 15% of websites need less resources to load. Javascripts take 52.9 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 6.9 kB

  • Original 9.7 kB
  • After minification 8.6 kB
  • After compression 2.9 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 1.2 kB, which is 12% 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 6.9 kB or 70% of the original size.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.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 32.0 kB or 60% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (73%)

Requests Now

30

After Optimization

8

  • Images
  • JavaScript
  • CSS

The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wam Leeds. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

wam.leeds.ac.uk

wam.leeds.ac.uk

360 ms

ProStyles.css

ProStyles.css

102 ms

styles.css

styles.css

264 ms

elcontent.js

elcontent.js

179 ms

common.js

common.js

270 ms

webbridge.js

webbridge.js

182 ms

new_example_set.css

new_example_set.css

266 ms

screen.css

screen.css

188 ms

screen-toolkit.css

screen-toolkit.css

272 ms

screen-library.css

screen-library.css

271 ms

tooltipster.css

tooltipster.css

278 ms

bibdisplay.js

bibdisplay.js

350 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

581 ms

systems.js

systems.js

354 ms

jquery.scrollbox.js

jquery.scrollbox.js

356 ms

jquery.tooltipster.min.js

jquery.tooltipster.min.js

451 ms

reset.css

reset.css

99 ms

forms.css

forms.css

173 ms

html_bg.png

html_bg.png

92 ms

container_shadow.png

container_shadow.png

93 ms

logo.png

logo.png

177 ms

logo_black.png

logo_black.png

94 ms

catalogue_green.png

catalogue_green.png

184 ms

ico_printer.gif

ico_printer.gif

93 ms

ico_rss.gif

ico_rss.gif

181 ms

tile_vgradient.jpg

tile_vgradient.jpg

172 ms

buttonspritecap.gif

buttonspritecap.gif

165 ms

buttonsprite.gif

buttonsprite.gif

167 ms

analytics.js

analytics.js

20 ms

collect

collect

25 ms

styles_print.css

styles_print.css

92 ms

SEO Factors

wam.leeds.ac.uk SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wam.leeds.ac.uk 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 Wam.leeds.ac.uk 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.

Social Sharing Optimization

wam.leeds.ac.uk

Open Graph description is not detected on the main page of Wam Leeds. 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: