3.6 sec in total
430 ms
2.9 sec
277 ms
Click here to check amazing Earthquake content for Switzerland. Otherwise, check out these important facts you probably never knew about earthquake.it
Elenco terremoti italiani e dal mondo, terremoti oggi e ieri, monitoraggio e mappe sismiche degli ultimi terremoti, le scale sismiche, cosa fare in caso di terremoto.
Visit earthquake.itWe analyzed Earthquake.it page load time and found that the first response time was 430 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
earthquake.it performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value3.6 s
61/100
25%
Value5.6 s
52/100
10%
Value1,270 ms
19/100
30%
Value0.414
24/100
15%
Value9.6 s
29/100
10%
430 ms
718 ms
211 ms
8 ms
262 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 12% of them (17 requests) were addressed to the original Earthquake.it, 9% (13 requests) were made to Maps.gstatic.com and 9% (13 requests) were made to S1.2mdn.net. The less responsive or slowest element that took the longest time to load (718 ms) belongs to the original domain Earthquake.it.
Page size can be reduced by 608.1 kB (47%)
1.3 MB
680.9 kB
In fact, the total size of Earthquake.it main page is 1.3 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. Javascripts take 660.6 kB which makes up the majority of the site volume.
Potential reduce by 150.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 150.2 kB or 88% of the original size.
Potential reduce by 11.4 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. Earthquake images are well optimized though.
Potential reduce by 436.2 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 436.2 kB or 66% of the original size.
Potential reduce by 10.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. Earthquake.it needs all CSS files to be minified and compressed as it can save up to 10.3 kB or 81% of the original size.
Number of requests can be reduced by 70 (54%)
130
60
The browser has sent 130 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Earthquake. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
earthquake.it
430 ms
www.earthquake.it
718 ms
terremoti.css
211 ms
adsbygoogle.js
8 ms
earthquake-350-2015.jpg
262 ms
earthquake-1000-2015.jpg
368 ms
cookieear.js
168 ms
ca-pub-8561033006186130.js
146 ms
zrt_lookup.html
134 ms
show_ads_impl.js
57 ms
gplus-32.png
117 ms
yellow.png
208 ms
green.png
208 ms
red.png
169 ms
blue.png
236 ms
laquila-1.jpg
240 ms
laquila-2.jpg
351 ms
laquila-3.jpg
352 ms
laquila-4.jpg
290 ms
laquila-5.jpg
413 ms
laquila-6.jpg
345 ms
clk.png
380 ms
ga.js
90 ms
platform.js
182 ms
jquery.min.js
88 ms
jquery.min.js
141 ms
ads
234 ms
osd.js
81 ms
ads
244 ms
ads
260 ms
__utm.gif
85 ms
cb=gapi.loaded_0
15 ms
cb=gapi.loaded_1
15 ms
page
191 ms
postmessageRelay
44 ms
182 ms
adj
127 ms
beacon
123 ms
3193398744-postmessagerelay.js
41 ms
rpc:shindig_random.js
71 ms
m_js_controller.js
79 ms
abg.js
116 ms
s_0R9dauzrbH_130649395.html
249 ms
cb=gapi.loaded_0
49 ms
rs=AGLTcCMsCOmPDrauiB2e0Q3LmfzOI69kWw
56 ms
rs=AGLTcCOJ4AMNA1EZSgGPzZnainRbXAPPWA
85 ms
rs=AGLTcCOmAbgwNnQOc2NYHnkILQFLDR0fBw
129 ms
favicon
268 ms
googlelogo_color_112x36dp.png
267 ms
nessie_icon_tiamat_white.png
99 ms
photo.jpg
269 ms
IMG_7813.JPG
366 ms
s
66 ms
x_button_blue2.png
54 ms
204 ms
0
416 ms
surly.js
267 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
295 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
313 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
333 ms
cl
313 ms
creative_add_on.js
376 ms
rs=AGLTcCOmAbgwNnQOc2NYHnkILQFLDR0fBw
93 ms
index.html
357 ms
verify_selector.js
260 ms
blank.gif
290 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
56 ms
rs=AGLTcCOmAbgwNnQOc2NYHnkILQFLDR0fBw
78 ms
ba.html
62 ms
pixel
86 ms
4.gif
83 ms
lidar.js
59 ms
sbhK2lTE.js
56 ms
cTrvNaRi.html
35 ms
4311.js
26 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
82 ms
pixel
93 ms
pixel
94 ms
surly.js
28 ms
verifyr.js
39 ms
index.html
57 ms
setuid
131 ms
2532.js
31 ms
beacon.js
100 ms
0
43 ms
bg.png
86 ms
adchoices.en.png
94 ms
styles.css
29 ms
sd
49 ms
faucet0.png
36 ms
faucet1.png
42 ms
faucet2.png
42 ms
t0.png
49 ms
t0_white.png
45 ms
t1.png
43 ms
logo.svg
45 ms
cta_bg.png
43 ms
cta_text.png
49 ms
FaceBody_300x250_logo.gif
77 ms
FaceBody_300x250_bg.jpg
104 ms
box_19_top-right.png
47 ms
bathroom_bg1.png
42 ms
bathroom_bg2.png
42 ms
ci.png
42 ms
js
68 ms
ui
147 ms
common.js
23 ms
map.js
24 ms
util.js
23 ms
marker.js
23 ms
activeview
61 ms
StaticMapService.GetMapImage
89 ms
onion.js
32 ms
openhand_8_8.cur
20 ms
ViewportInfoService.GetViewportInfo
30 ms
stats.js
23 ms
transparent.png
25 ms
kh
21 ms
kh
21 ms
controls.js
18 ms
kh
56 ms
kh
55 ms
kh
57 ms
kh
57 ms
infowindow.js
48 ms
css
54 ms
mm_20_yellow.png
37 ms
google4.png
35 ms
mm_20_green.png
24 ms
mm_20_red.png
25 ms
mapcnt6.png
24 ms
sv5.png
25 ms
AuthenticationService.Authenticate
138 ms
mm_20_yellow.png
19 ms
tmapctrl.png
22 ms
cb_scout5.png
23 ms
tmapctrl4.png
21 ms
imgs8.png
21 ms
google_white5.png
21 ms
mm_20_green.png
21 ms
mm_20_red.png
26 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
14 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
14 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
14 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
13 ms
earthquake.it 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-*] attributes do not match their roles
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
earthquake.it best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
earthquake.it SEO score
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
IT
IT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Earthquake.it can be misinterpreted by Google and other search engines. Our service has detected that Italian is used on the page, and it matches the claimed language. Our system also found out that Earthquake.it 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.
earthquake.it
Open Graph description is not detected on the main page of Earthquake. 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: