3.9 sec in total
355 ms
3.4 sec
203 ms
Welcome to grace.ac.uk homepage info - get ready to check Grace best content right away, or after learning these important things about grace.ac.uk
The University of Nottingham is a pioneering institution. We’re a top 20 UK university and 8th in the UK for research power. We’re working to change the world.
Visit grace.ac.ukWe analyzed Grace.ac.uk page load time and found that the first response time was 355 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
grace.ac.uk performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value17.5 s
0/100
25%
Value8.4 s
18/100
10%
Value1,770 ms
10/100
30%
Value0.07
96/100
15%
Value23.2 s
1/100
10%
355 ms
293 ms
903 ms
495 ms
262 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Grace.ac.uk, 61% (33 requests) were made to Nottingham.ac.uk and 13% (7 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Nottingham.ac.uk.
Page size can be reduced by 623.4 kB (27%)
2.3 MB
1.7 MB
In fact, the total size of Grace.ac.uk main page is 2.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 32.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. 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 32.2 kB or 75% of the original size.
Potential reduce by 303.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. Obviously, Grace needs image optimization as it can save up to 303.1 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 164.2 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 164.2 kB or 68% of the original size.
Potential reduce by 124.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. Grace.ac.uk needs all CSS files to be minified and compressed as it can save up to 124.0 kB or 85% of the original size.
Number of requests can be reduced by 32 (65%)
49
17
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grace. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
grace.ac.uk
355 ms
grace
293 ms
index.aspx
903 ms
globalfornonuonnew.css
495 ms
grace.css
262 ms
WebResource.axd
594 ms
WebResource.axd
353 ms
WebResource.axd
262 ms
WebResource.axd
191 ms
WebResource.axd
614 ms
thickbox.js
440 ms
thickbox.css
371 ms
Responsive.css
436 ms
global.js
459 ms
internal.js
521 ms
uon-ui.js
524 ms
jquery-cookiebar.js
546 ms
slicknav.js
576 ms
gaclicktracking.js
618 ms
WebResource.axd
693 ms
ScriptResource.axd
876 ms
ScriptResource.axd
672 ms
ga.js
5 ms
GRACE-star-CMYK.png
103 ms
CachedImage.axd
910 ms
CachedImage.axd
1151 ms
CachedImage.axd
1055 ms
UoN.png
177 ms
__utm.gif
13 ms
collect
61 ms
ga-audiences
33 ms
background-page.png
110 ms
bg-textOverlay-GRACE.png
112 ms
bg-textOverlay-darkGrey.png
111 ms
bg-icon-facebook.png
186 ms
bg-icon-twitter-bird.png
197 ms
widgets.js
56 ms
mailchimp.html
266 ms
loader.gif
196 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
24 ms
syndication
87 ms
368310416968929280
181 ms
proxy.jpg
118 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
7 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
9 ms
grace_star_normal.PNG
87 ms
ZhuMb78o_normal.jpg
126 ms
Mv4fgDci_normal.jpg
87 ms
9rxnmcYV_normal.jpeg
87 ms
9bb1a7b80c6b8007def31f08caddaf42_normal.jpeg
86 ms
CbgK5XJWAAArWwQ.png:small
167 ms
CbXNhZNXEAAQGFg.jpg:small
265 ms
jot
24 ms
nr-100.js
16 ms
grace.ac.uk accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
grace.ac.uk 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
Page has valid source maps
grace.ac.uk 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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 Grace.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 Grace.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.
grace.ac.uk
Open Graph description is not detected on the main page of Grace. 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: