4.1 sec in total
404 ms
3.5 sec
222 ms
Click here to check amazing SUMaC Stanford content for United States. Otherwise, check out these important facts you probably never knew about sumac.stanford.edu
Visit sumac.stanford.eduWe analyzed Sumac.stanford.edu page load time and found that the first response time was 404 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
sumac.stanford.edu performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value7.2 s
5/100
25%
Value6.3 s
42/100
10%
Value970 ms
28/100
30%
Value0
100/100
15%
Value15.1 s
7/100
10%
404 ms
1334 ms
86 ms
170 ms
253 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 90% of them (65 requests) were addressed to the original Sumac.stanford.edu, 4% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Sumac.stanford.edu.
Page size can be reduced by 527.3 kB (30%)
1.8 MB
1.2 MB
In fact, the total size of Sumac.stanford.edu main page is 1.8 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.2 MB which makes up the majority of the site volume.
Potential reduce by 25.0 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 25.0 kB or 80% of the original size.
Potential reduce by 115.9 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. SUMaC Stanford images are well optimized though.
Potential reduce by 130.8 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 130.8 kB or 63% of the original size.
Potential reduce by 255.6 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. Sumac.stanford.edu needs all CSS files to be minified and compressed as it can save up to 255.6 kB or 83% of the original size.
Number of requests can be reduced by 51 (77%)
66
15
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SUMaC Stanford. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 34 to 1 for CSS and as a result speed up the page load time.
sumac.stanford.edu
404 ms
sumac.stanford.edu
1334 ms
system.base.css
86 ms
system.menus.css
170 ms
system.messages.css
253 ms
system.theme.css
270 ms
jquery.ui.core.css
256 ms
jquery.ui.theme.css
335 ms
jquery.ui.accordion.css
339 ms
calendar_multiday.css
355 ms
comment.css
418 ms
date.css
422 ms
datepicker.1.7.css
425 ms
field.css
438 ms
mollom.css
436 ms
node.css
461 ms
poll.css
501 ms
search.css
503 ms
stanford_carousel.css
505 ms
user.css
519 ms
views.css
518 ms
context_accordion.css
548 ms
ctools.css
581 ms
bootstrap.min.css
673 ms
bootstrap-responsive.min.css
588 ms
font-awesome.min.css
601 ms
open_framework.css
604 ms
stanford-framework.css
637 ms
stanford-default.css
666 ms
ie.css
670 ms
open_framework_print.css
687 ms
css_injector_1.css
688 ms
css_injector_3.css
725 ms
css_injector_5.css
747 ms
jquery-1.9.1.min.js
837 ms
jquery-migrate-1.2.1.min.js
753 ms
jquery.once.js
770 ms
drupal.js
769 ms
jquery.ui.core.min.js
740 ms
jquery.ui.widget.min.js
675 ms
jquery.ui.accordion.min.js
625 ms
stanford_carousel.js
624 ms
stanford_event_nodes.js
610 ms
stanford_events_calendar.js
577 ms
context_accordion.js
587 ms
googleanalytics.js
573 ms
bootstrap.min.js
516 ms
open_framework.js
528 ms
jquery.placeholder.min.js
525 ms
override.js
565 ms
stanford-framework.js
570 ms
stanford_carousel_aria.js
549 ms
css
60 ms
css
73 ms
analytics.js
44 ms
collect
23 ms
header-stanford-logo@2x.png
91 ms
logo.png
110 ms
searchbutton.png
90 ms
sumac-6_2.jpg
664 ms
sumac-13.jpg
660 ms
sumac-1.jpg
664 ms
btn-arrow-left.png
166 ms
btn-arrow-right.png
168 ms
sumac-8.jpg
355 ms
sumac-9.jpg
329 ms
sumac-4.jpg
417 ms
footer-stanford-logo@2x.png
413 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
50 ms
toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf
63 ms
toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf
86 ms
fontawesome-webfont.woff
444 ms
sumac.stanford.edu 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 IDs are not unique
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
<frame> or <iframe> elements do not have a title
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
sumac.stanford.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
sumac.stanford.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 Sumac.stanford.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 Sumac.stanford.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.
sumac.stanford.edu
Open Graph description is not detected on the main page of SUMaC Stanford. 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: