1.1 sec in total
142 ms
834 ms
128 ms
Welcome to discovere.emory.edu homepage info - get ready to check Discovere Emory best content for United States right away, or after learning these important things about discovere.emory.edu
Visit discovere.emory.eduWe analyzed Discovere.emory.edu page load time and found that the first response time was 142 ms and then it took 962 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
discovere.emory.edu performance score
name
value
score
weighting
Value11.4 s
0/100
10%
Value14.1 s
0/100
25%
Value11.4 s
5/100
10%
Value1,890 ms
8/100
30%
Value0.003
100/100
15%
Value18.1 s
3/100
10%
142 ms
143 ms
61 ms
211 ms
87 ms
Our browser made a total of 30 requests to load all elements on the main page. We found that 50% of them (15 requests) were addressed to the original Discovere.emory.edu, 27% (8 requests) were made to Web.library.emory.edu and 13% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (211 ms) belongs to the original domain Discovere.emory.edu.
Page size can be reduced by 112.1 kB (62%)
179.8 kB
67.6 kB
In fact, the total size of Discovere.emory.edu main page is 179.8 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 93.9 kB which makes up the majority of the site volume.
Potential reduce by 54.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 29.3 kB, which is 46% 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 54.9 kB or 86% of the original size.
Potential reduce by 4.3 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, Discovere Emory needs image optimization as it can save up to 4.3 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 50.1 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 50.1 kB or 53% of the original size.
Potential reduce by 2.9 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. Discovere.emory.edu needs all CSS files to be minified and compressed as it can save up to 2.9 kB or 56% of the original size.
Number of requests can be reduced by 15 (54%)
28
13
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Discovere Emory. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
search.do
142 ms
primo_library_wro_discovere_en_US.css
143 ms
primo_library_wro_discovere_en_US.js
61 ms
primo_library_web.js
211 ms
add2home.js
87 ms
add2home.css
65 ms
yahoo-min.js
62 ms
dom-min.js
99 ms
event-min.js
69 ms
main.js
62 ms
jquery.inputTip.js
59 ms
jquery-ui.min.js
71 ms
global.js
66 ms
search.js
101 ms
quicklinks.js
93 ms
discovere.js
63 ms
pleaseWait.js
29 ms
banner.png
32 ms
analytics.js
32 ms
global-nav-logo.jpg
30 ms
lits-discovere.png
62 ms
icon_star_on.png
38 ms
linkid.js
12 ms
icon_clear_search.png
40 ms
bg_strip_footer.png
35 ms
ask-librarian-clear.png
36 ms
collect
23 ms
collect
23 ms
footer_emory_libraries.gif
32 ms
collect
59 ms
discovere.emory.edu accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
discovere.emory.edu 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
discovere.emory.edu SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Discovere.emory.edu can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Discovere.emory.edu 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.
discovere.emory.edu
Open Graph description is not detected on the main page of Discovere Emory. 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: