2.5 sec in total
308 ms
2 sec
200 ms
Click here to check amazing Lightning Maps content for Poland. Otherwise, check out these important facts you probably never knew about lightningmaps.org
See lightning strikes in real time across the planet. Free access to maps of former thunderstorms. By Blitzortung.org and contributors.
Visit lightningmaps.orgWe analyzed Lightningmaps.org page load time and found that the first response time was 308 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
lightningmaps.org performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value6.2 s
11/100
25%
Value8.0 s
21/100
10%
Value730 ms
41/100
30%
Value0.007
100/100
15%
Value7.8 s
44/100
10%
308 ms
109 ms
95 ms
186 ms
183 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 30% of them (37 requests) were addressed to the original Lightningmaps.org, 34% (42 requests) were made to Maps.googleapis.com and 12% (15 requests) were made to Khm0.googleapis.com. The less responsive or slowest element that took the longest time to load (465 ms) belongs to the original domain Lightningmaps.org.
Page size can be reduced by 699.9 kB (50%)
1.4 MB
686.5 kB
In fact, the total size of Lightningmaps.org main page is 1.4 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 846.9 kB which makes up the majority of the site volume.
Potential reduce by 55.6 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 55.6 kB or 86% of the original size.
Potential reduce by 24.0 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. Lightning Maps images are well optimized though.
Potential reduce by 618.0 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 618.0 kB or 73% of the original size.
Potential reduce by 2.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. Lightningmaps.org needs all CSS files to be minified and compressed as it can save up to 2.3 kB or 69% of the original size.
Number of requests can be reduced by 50 (43%)
117
67
The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lightning Maps. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
lightningmaps.org
308 ms
realtime
109 ms
index.php
95 ms
index.php
186 ms
index.php
183 ms
jquery.js
465 ms
index.php
201 ms
index.php
199 ms
js
40 ms
index.php
201 ms
Blitzortung_Logo.jpg
95 ms
facebook.png
92 ms
googleplus.png
95 ms
twitter.png
187 ms
en.png
98 ms
de.png
180 ms
fr.png
184 ms
it.png
185 ms
hu.png
190 ms
nl.png
268 ms
lv.png
305 ms
fi.png
304 ms
sv.png
304 ms
pl.png
304 ms
cz.png
392 ms
dk.png
392 ms
title_background2.jpg
242 ms
blitz_gelb.png
103 ms
world.png
102 ms
flag_eu_menu.png
106 ms
flag_au_menu.png
183 ms
flag_us_menu.png
189 ms
index.php
291 ms
common.js
22 ms
map.js
21 ms
piwik.js
261 ms
util.js
53 ms
onion.js
21 ms
openhand_8_8.cur
44 ms
ViewportInfoService.GetViewportInfo
93 ms
stats.js
28 ms
kh
72 ms
kh
73 ms
controls.js
58 ms
kh
65 ms
kh
71 ms
kh
123 ms
kh
73 ms
kh
73 ms
kh
68 ms
kh
112 ms
kh
116 ms
kh
119 ms
kh
117 ms
kh
118 ms
kh
120 ms
kh
122 ms
kh
123 ms
kh
61 ms
kh
64 ms
kh
64 ms
kh
65 ms
kh
67 ms
kh
65 ms
kh
66 ms
kh
117 ms
kh
109 ms
kh
112 ms
kh
110 ms
kh
110 ms
kh
114 ms
kh
116 ms
transparent.png
52 ms
info.png
119 ms
blitz.png
118 ms
speaker_black.png
118 ms
speaker_blue.png
116 ms
gear.png
118 ms
css
75 ms
google4.png
45 ms
vt
24 ms
vt
43 ms
vt
42 ms
vt
42 ms
vt
42 ms
vt
44 ms
vt
42 ms
vt
44 ms
vt
44 ms
vt
45 ms
vt
46 ms
vt
46 ms
vt
47 ms
vt
47 ms
vt
47 ms
vt
54 ms
vt
54 ms
vt
56 ms
vt
54 ms
vt
56 ms
vt
56 ms
vt
57 ms
vt
58 ms
vt
58 ms
vt
57 ms
vt
58 ms
vt
62 ms
vt
62 ms
vt
63 ms
vt
69 ms
vt
68 ms
vt
67 ms
mapcnt6.png
40 ms
tmapctrl.png
28 ms
tmapctrl4.png
35 ms
imgs8.png
36 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
26 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
32 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
43 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
47 ms
AuthenticationService.Authenticate
16 ms
marker.js
12 ms
cookieconsent2.css
102 ms
lightningmaps.org 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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
lightningmaps.org 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
lightningmaps.org 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
EN
EN
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lightningmaps.org 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 Lightningmaps.org main page’s claimed encoding is . 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.
lightningmaps.org
Open Graph description is not detected on the main page of Lightning Maps. 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: