8.9 sec in total
58 ms
4.6 sec
4.2 sec
Welcome to scotusblog.com homepage info - get ready to check SCOTUSblog best content for United States right away, or after learning these important things about scotusblog.com
Devoted to covering the US Supreme Court comprehensively, without bias according to the highest journalistic standards as a public service
Visit scotusblog.comWe analyzed Scotusblog.com page load time and found that the first response time was 58 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
scotusblog.com performance score
name
value
score
weighting
Value9.5 s
0/100
10%
Value14.6 s
0/100
25%
Value16.3 s
0/100
10%
Value8,140 ms
0/100
30%
Value0.092
91/100
15%
Value29.0 s
0/100
10%
58 ms
121 ms
81 ms
18 ms
34 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 49% of them (55 requests) were addressed to the original Scotusblog.com, 13% (14 requests) were made to Pbs.twimg.com and 8% (9 requests) were made to Sblog.s3.amazonaws.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source C.statcounter.com.
Page size can be reduced by 687.0 kB (20%)
3.5 MB
2.8 MB
In fact, the total size of Scotusblog.com main page is 3.5 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 112.8 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 112.8 kB or 81% of the original size.
Potential reduce by 102.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. SCOTUSblog images are well optimized though.
Potential reduce by 398.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 398.9 kB or 63% of the original size.
Potential reduce by 73.3 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. Scotusblog.com needs all CSS files to be minified and compressed as it can save up to 73.3 kB or 80% of the original size.
Number of requests can be reduced by 48 (44%)
108
60
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SCOTUSblog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
scotusblog.com
58 ms
www.scotusblog.com
121 ms
style.css
81 ms
jquery.min.js
18 ms
jquery-ui.min.js
34 ms
mail_defence.js
41 ms
ash.js
79 ms
widget.js
370 ms
jquery.cycle.all.js
380 ms
twitter-feed.css
77 ms
jquery.js
489 ms
jquery-migrate.min.js
360 ms
jquery-ui-1.8.16.custom.min.js
602 ms
ddpowerzoomer.js
359 ms
jquery.sspowerzoomer.js
361 ms
buttons.js
22 ms
ash.js
358 ms
footer_js.js
432 ms
superfish.js
421 ms
jquery.hoverIntent.minified.js
524 ms
jquery.newsticker.pack.js
525 ms
addthis_widget.js
772 ms
simple.accordion.js
539 ms
wp-emoji-release.min.js
566 ms
ga.js
405 ms
quant.js
428 ms
email12x12.png
627 ms
steve-wermiel.jpg
611 ms
Banner160214.4-3.jpg
590 ms
scotusblog-logo.png
292 ms
5-5-14_home_blue.png
315 ms
5-5-14_mertiscases_blue.png
314 ms
5-5-14_petitions_blue.png
291 ms
5-5-14_stats_blue.png
589 ms
5-5-14_specialfeatures_blue.png
589 ms
5-5-14_plainenglish_blue.png
591 ms
5-5-14_videos_blue.png
590 ms
5-5-14_resources_blue.png
588 ms
5-5-14_admin_blue.png
627 ms
btn-close.png
625 ms
print_s.png
624 ms
arrow-accordion.png
625 ms
Screen-Shot-2016-02-11-at-10.48.35-AM-277x207.png
658 ms
Peabody-medallion_w120.jpg
628 ms
sdx_medalion.png
660 ms
NPC_logotype_RGB-300x150.jpg
635 ms
sgavel21.jpg
658 ms
aja.png
626 ms
webby_awards.jpg
626 ms
AndrewMasthead4.png
630 ms
Molly-thumbnail.jpg
630 ms
ronald-mann.jpg
627 ms
Art_Lien_110x110.jpg
645 ms
rory-little3.jpg
678 ms
fabrizio-di-piazza.png
646 ms
mwalsh.png
647 ms
2013_Baude_Studio-8348c-11.jpg
698 ms
Bhatia_SCOTUSblog.jpg
647 ms
Victoria-Kwan-headshot-12.2014.jpg
648 ms
Unknown.jpeg
637 ms
tom-goldstein.jpg
547 ms
amy-howe.jpg
546 ms
lyle-denniston.jpg
547 ms
john-elwood.jpg
545 ms
tejinder-singh.jpg
545 ms
amanda-frost.jpg
568 ms
kevin-russell.jpg
558 ms
kevin-johnson.jpg
556 ms
ronald-collins.jpg
543 ms
__utm.gif
203 ms
widgets.js
64 ms
mobile.css
123 ms
widget70.css
114 ms
counter_xhtml.js
23 ms
t.php
1260 ms
pixel;r=1467147238;a=p-Bdm45S1B4jjyS;fpan=1;fpa=P0-163434122-1455623410706;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1455623410706;tzo=-180;ref=;url=http%3A%2F%2Fwww.scotusblog.com%2F;ogl=locale.en_US%2Csite_name.SCOTUSblog%2Ctitle.SCOTUSblog%2Curl.http%3A%2F%2Fwww%252Escotusblog%252Ecom%2Ctype.website%2Cdescription.The%20Supreme%20Court%20of%20the%20United%20States%20blog
1225 ms
arrow-accordion-active.png
742 ms
timeline.fe2df323b0284f547735e29f610f34bf.js
520 ms
getAllAppDefault.esi
320 ms
sh64.html
117 ms
syndication
384 ms
346583495973425152
494 ms
getSegment.php
92 ms
checkOAuth.esi
14 ms
t.dhj
29 ms
t.dhj
63 ms
cm
208 ms
s-3271.xgi
150 ms
hbpix
211 ms
161 ms
timeline.d6812d7a233cc6acdaf452b485c20172.default.css
47 ms
timeline.d6812d7a233cc6acdaf452b485c20172.default.css
59 ms
pixel
98 ms
64 ms
xrefid.xgi
63 ms
pixel
97 ms
8z9FImcv_normal.png
302 ms
VXVX-Xbi_normal.jpeg
293 ms
vU0ZvBDn_normal.jpeg
297 ms
d1aa41b411da85811704203729a25ff0_normal.jpeg
282 ms
5fPOs_OR_normal.jpeg
313 ms
SHERMAN__Mark_normal.jpg
284 ms
YI4gl12-_normal.png
287 ms
qwcudOGZ_normal.jpeg
274 ms
i-cFr9Ht_normal.jpg
275 ms
y4ZEbhPH_normal.png
286 ms
RJWpfsWX_normal.jpeg
284 ms
Uy_rPcnx_normal.jpeg
283 ms
CbLjLdGW0AAzEdF.jpg:small
283 ms
CbIOYbWWwAI6jPe.jpg:small
298 ms
2981
239 ms
chartbeat.js
48 ms
scotusblog.com 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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
scotusblog.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
scotusblog.com 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
Image elements do not have [alt] attributes
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 Scotusblog.com 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 Scotusblog.com 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.
scotusblog.com
Open Graph data is detected on the main page of SCOTUSblog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: