2.5 sec in total
317 ms
1.9 sec
247 ms
Welcome to seismo.berkeley.edu homepage info - get ready to check Seismo Berkeley best content for United States right away, or after learning these important things about seismo.berkeley.edu
UC Berkeley Seismological Lab
Visit seismo.berkeley.eduWe analyzed Seismo.berkeley.edu page load time and found that the first response time was 317 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
seismo.berkeley.edu performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value15.6 s
0/100
25%
Value4.8 s
66/100
10%
Value110 ms
97/100
30%
Value0.009
100/100
15%
Value7.4 s
49/100
10%
317 ms
157 ms
377 ms
159 ms
159 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 42% of them (33 requests) were addressed to the original Seismo.berkeley.edu, 22% (17 requests) were made to Maps.google.com and 9% (7 requests) were made to Ncedc.org. The less responsive or slowest element that took the longest time to load (862 ms) belongs to the original domain Seismo.berkeley.edu.
Page size can be reduced by 596.3 kB (39%)
1.5 MB
915.7 kB
In fact, the total size of Seismo.berkeley.edu main page is 1.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. 55% of websites need less resources to load. Javascripts take 761.1 kB which makes up the majority of the site volume.
Potential reduce by 28.5 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 5.4 kB, which is 15% 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 28.5 kB or 82% of the original size.
Potential reduce by 29.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. Seismo Berkeley images are well optimized though.
Potential reduce by 521.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 521.9 kB or 69% of the original size.
Potential reduce by 16.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. Seismo.berkeley.edu needs all CSS files to be minified and compressed as it can save up to 16.9 kB or 82% of the original size.
Number of requests can be reduced by 23 (32%)
72
49
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Seismo Berkeley. 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 6 to 1 for CSS and as a result speed up the page load time.
seismo.berkeley.edu
317 ms
bsl_2013.css
157 ms
jquery.min.js
377 ms
iPhoneiPad.js
159 ms
getyear.js
159 ms
skipLinkScript.js
166 ms
jenHomepageFix.css
224 ms
jquery.bxslider.min.js
407 ms
jquery.bxslider.css
311 ms
brand
17 ms
brand
106 ms
ga.js
67 ms
en-play-badge.png
145 ms
Twitter_logo_white.png
156 ms
YouTube_light_color_icon.png
162 ms
rss_button.png
156 ms
SSSS_20130206_transparent.png
160 ms
BSLlogo_forweb_75pct.jpg
234 ms
BSLLogoGrayscaleNoBorder.jpg
162 ms
TheMWCTeam_homepageSlide.jpg
387 ms
cmsb_homepage_slide.jpg
392 ms
RanNof_homepage_slide.jpg
317 ms
tcas_homepage_slide1.jpg
387 ms
WHResilience_homepage_slide.jpg
317 ms
tcas_homepage_slide2.jpg
467 ms
eos_nuc_story_size.jpg
542 ms
MyShake_slide.png
471 ms
Getty_477117851_web.jpg
614 ms
newsCarousel_20160202.png
768 ms
2015_blog_0903_plume.png
693 ms
homepageSlideChaussardCalaveras.png
862 ms
10s_Warning.png
773 ms
ucseal_540_874.gif
694 ms
bearpaw.gif
758 ms
google_custom_search_watermark.gif
88 ms
246 ms
__utm.gif
34 ms
google_custom_search_watermark.gif
33 ms
bx_loader.gif
726 ms
controls.png
727 ms
js
64 ms
prototype.js
539 ms
seismap.js
230 ms
seismap.css
156 ms
common.js
17 ms
map.js
34 ms
SPACER
96 ms
LEGEND
95 ms
BSL
97 ms
StaticMapService.GetMapImage
191 ms
bsl_2013_print.css
94 ms
util.js
16 ms
onion.js
16 ms
openhand_8_8.cur
42 ms
ViewportInfoService.GetViewportInfo
84 ms
stats.js
33 ms
controls.js
33 ms
transparent.png
17 ms
css
60 ms
google4.png
46 ms
mapcnt6.png
37 ms
vt
15 ms
vt
17 ms
vt
18 ms
vt
29 ms
vt
25 ms
vt
29 ms
vt
25 ms
vt
24 ms
vt
26 ms
vt
33 ms
tmapctrl.png
17 ms
tmapctrl4.png
27 ms
imgs8.png
27 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
30 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
40 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
56 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
58 ms
AuthenticationService.Authenticate
100 ms
seismo.berkeley.edu accessibility score
seismo.berkeley.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
seismo.berkeley.edu SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Seismo.berkeley.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 Seismo.berkeley.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.
seismo.berkeley.edu
Open Graph description is not detected on the main page of Seismo Berkeley. 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: