1.5 sec in total
97 ms
1.1 sec
385 ms
Visit mrsec.duke.edu now to see the best up-to-date Mrsec Duke content for United States and also check out these interesting facts you probably never knew about mrsec.duke.edu
Visit mrsec.duke.eduWe analyzed Mrsec.duke.edu page load time and found that the first response time was 97 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 30% of websites can load faster.
mrsec.duke.edu performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value10.4 s
0/100
25%
Value8.9 s
15/100
10%
Value1,760 ms
10/100
30%
Value0.208
60/100
15%
Value21.0 s
1/100
10%
97 ms
49 ms
24 ms
52 ms
102 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Mrsec.duke.edu, 73% (51 requests) were made to Pratt.duke.edu and 10% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (320 ms) relates to the external source Pratt.duke.edu.
Page size can be reduced by 276.6 kB (30%)
934.0 kB
657.4 kB
In fact, the total size of Mrsec.duke.edu main page is 934.0 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. 55% of websites need less resources to load. Images take 473.3 kB which makes up the majority of the site volume.
Potential reduce by 68.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 68.2 kB or 79% of the original size.
Potential reduce by 202.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, Mrsec Duke needs image optimization as it can save up to 202.1 kB or 43% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 4.5 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. Mrsec.duke.edu has all CSS files already compressed.
Number of requests can be reduced by 46 (77%)
60
14
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mrsec Duke. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
mrsec.duke.edu
97 ms
49 ms
duke_audit.css
24 ms
sbi-styles.min.css
52 ms
style.min.css
102 ms
pratt-people-admin.css
83 ms
index.css
106 ms
front.min.css
84 ms
jquery.min.js
105 ms
jquery-migrate.min.js
112 ms
accordion.js
112 ms
posts-year-filter.js
123 ms
page-header-play-button.js
128 ms
faculty-overview-toggle.js
128 ms
header.js
130 ms
sidebar.js
132 ms
social-share.js
145 ms
timeline.js
150 ms
counter.js
150 ms
front.min.js
152 ms
pratt-people-public.js
154 ms
sidebarv2.js
28 ms
alert.css
162 ms
alert.html
164 ms
new-tab.js
227 ms
api.js
36 ms
dom-ready.min.js
227 ms
hooks.min.js
228 ms
i18n.min.js
228 ms
a11y.min.js
231 ms
jquery.json.min.js
231 ms
gravityforms.min.js
230 ms
utils.min.js
230 ms
vendor-theme.min.js
318 ms
scripts-theme.min.js
317 ms
frontend-legacy.min.js
317 ms
ping
44 ms
embed.js
37 ms
css2
32 ms
css2
61 ms
gtm.js
182 ms
gtm.js
214 ms
sbi-sprite.png
100 ms
duke-pratt-navy-logo.png
100 ms
down-caret.svg
126 ms
search.svg
127 ms
arrow-midnight.svg
124 ms
AdobeStock_615440931.jpeg
320 ms
arrow.svg
126 ms
IMG_6216-scaled-e1706204519692-380x260.jpg
148 ms
voxel-finished-staples-760x520.jpg
194 ms
dalton-concrete-760x520.jpg
214 ms
duke-pratt-white-logo.png
145 ms
facebook.svg
167 ms
instagram.svg
170 ms
twitter.svg
193 ms
youtube.svg
195 ms
linkedin.svg
211 ms
map-marker.svg
213 ms
phone.svg
211 ms
duke-100-white.svg
215 ms
KFOmCnqEu92Fr1Me5Q.ttf
103 ms
KFOlCnqEu92Fr1MmEU9vAw.ttf
114 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
114 ms
u-4n0qyriQwlOrhSvowK_l52xwNpXw.ttf
22 ms
KFOkCnqEu92Fr1Mu52xP.ttf
21 ms
KFOjCnqEu92Fr1Mu51S7ABc9.ttf
21 ms
KFOjCnqEu92Fr1Mu51TzBhc9.ttf
20 ms
54 ms
recaptcha__en.js
23 ms
mrsec.duke.edu accessibility score
mrsec.duke.edu 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
Browser errors were logged to the console
Page has valid source maps
mrsec.duke.edu SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mrsec.duke.edu 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 Mrsec.duke.edu main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
mrsec.duke.edu
Open Graph description is not detected on the main page of Mrsec Duke. 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: