918 ms in total
152 ms
612 ms
154 ms
Welcome to registrar.duke.edu homepage info - get ready to check Registrar Duke best content for United States right away, or after learning these important things about registrar.duke.edu
Homepage - Office of the University Registrar
Visit registrar.duke.eduWe analyzed Registrar.duke.edu page load time and found that the first response time was 152 ms and then it took 766 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.
registrar.duke.edu performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value3.7 s
58/100
25%
Value3.0 s
94/100
10%
Value150 ms
94/100
30%
Value0.717
7/100
15%
Value4.1 s
87/100
10%
152 ms
40 ms
40 ms
49 ms
49 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 86% of them (60 requests) were addressed to the original Registrar.duke.edu, 7% (5 requests) were made to Brandbar.oit.duke.edu and 3% (2 requests) were made to Alertbar.oit.duke.edu. The less responsive or slowest element that took the longest time to load (258 ms) belongs to the original domain Registrar.duke.edu.
Page size can be reduced by 222.1 kB (48%)
463.6 kB
241.4 kB
In fact, the total size of Registrar.duke.edu main page is 463.6 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. 25% of websites need less resources to load. Images take 175.4 kB which makes up the majority of the site volume.
Potential reduce by 26.1 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 26.1 kB or 78% of the original size.
Potential reduce by 14.2 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. Registrar Duke images are well optimized though.
Potential reduce by 114.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 114.9 kB or 68% of the original size.
Potential reduce by 66.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. Registrar.duke.edu needs all CSS files to be minified and compressed as it can save up to 66.9 kB or 77% of the original size.
Number of requests can be reduced by 44 (64%)
69
25
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Registrar 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 6 to 1 for JavaScripts and from 40 to 1 for CSS and as a result speed up the page load time.
registrar.duke.edu
152 ms
system.base.css
40 ms
system.menus.css
40 ms
system.messages.css
49 ms
system.theme.css
49 ms
calendar_multiday.css
55 ms
date.css
52 ms
field.css
93 ms
node.css
93 ms
search.css
92 ms
user.css
92 ms
views.css
91 ms
ctools.css
101 ms
panels.css
138 ms
shib_auth.css
137 ms
3col-even.css
136 ms
flexible.css
135 ms
ccb5205ee4e299c97de3f4f1ea163217.css
135 ms
alert.css
180 ms
main-menu.css
150 ms
gold-callout.css
166 ms
contact-info.css
168 ms
gold-heading.css
175 ms
alpha-reset.css
173 ms
alpha-mobile.css
173 ms
alpha-alpha.css
180 ms
formalize.css
196 ms
omega-text.css
196 ms
omega-branding.css
201 ms
omega-menu.css
199 ms
omega-forms.css
200 ms
omega-visuals.css
211 ms
global.css
226 ms
duke-standard-alpha-default.css
226 ms
duke-standard-alpha-default-normal.css
227 ms
registrar-alpha-default.css
227 ms
registrar-alpha-default-normal.css
227 ms
footer.css
163 ms
alert.html
164 ms
build_footer.php
166 ms
alpha-default-normal-12.css
233 ms
alpha-default-normal-24.css
242 ms
js_UWQINlriydSoeSiGQxToOUdv493zEa7dpsXC1OtYlZU.js
258 ms
js_I8yX6RYPZb7AtMcDUA3QKDZqVkvEn35ED11_1i7vVpc.js
236 ms
js_8xTTE3pae-Vxxl-KA6-DWKFaNYfZp976AGpsw0qbKkY.js
233 ms
js_V0xYa_dHQO_ObUqoC7OXo03lX-M0FTsNpBu1tLnmWTw.js
234 ms
js_43n5FBy8pZxQHxPXkf-sQF7ZiacVZke14b0VlvSA554.js
240 ms
omega_18.css
172 ms
analytics.js
28 ms
WrdqIVDJ_normal.jpeg
17 ms
region-branding-bg.png
55 ms
logo.png
52 ms
registrar-logo.png
52 ms
search-left-edge.png
53 ms
btn-search-go.png
52 ms
img_home_720x280.jpg
84 ms
disclosure-triangle-right.png
56 ms
block-header-bg.png
57 ms
gold-square.png
59 ms
twitter.png
60 ms
facebook.png
69 ms
instagram.png
87 ms
li-square.png
89 ms
twitter-block-birdie.png
91 ms
logo-scd1ded5892.png
27 ms
collect
26 ms
footer_rule.png
17 ms
icons-s897ae9cbcb.png
20 ms
block-header-curl.png
58 ms
page-shadow.png
20 ms
registrar.duke.edu accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
registrar.duke.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
Page has valid source maps
registrar.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Registrar.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 Registrar.duke.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.
registrar.duke.edu
Open Graph description is not detected on the main page of Registrar 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: