20.7 sec in total
191 ms
20.4 sec
145 ms
Visit legoblockshell.org now to see the best up-to-date Legoblockshell content and also check out these interesting facts you probably never knew about legoblockshell.org
Sign the petition to ask LEGO to cut ties with Shell and save the Arctic. Don't let Shell pollute our children's minds!
Visit legoblockshell.orgWe analyzed Legoblockshell.org page load time and found that the first response time was 191 ms and then it took 20.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
legoblockshell.org performance score
191 ms
192 ms
40 ms
53 ms
488 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Legoblockshell.org, 23% (16 requests) were made to Secured-static.greenpeace.org and 12% (8 requests) were made to Lib.greenpeace.se. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Aurora.grnpc.org.
Page size can be reduced by 698.7 kB (31%)
2.3 MB
1.6 MB
In fact, the total size of Legoblockshell.org main page is 2.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. 45% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 22.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. This page needs HTML code to be minified as it can gain 4.8 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 22.8 kB or 73% of the original size.
Potential reduce by 20.2 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. Legoblockshell images are well optimized though.
Potential reduce by 609.3 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 609.3 kB or 68% of the original size.
Potential reduce by 46.5 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. Legoblockshell.org needs all CSS files to be minified and compressed as it can save up to 46.5 kB or 85% of the original size.
Number of requests can be reduced by 29 (57%)
51
22
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Legoblockshell. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
legoblockshell.org
191 ms
action
192 ms
css
40 ms
css
53 ms
style.css
488 ms
ensharing.css
61 ms
typeahead.css
94 ms
main.css
657 ms
jquery.js
31 ms
main.js
678 ms
jsapi
65 ms
eaCommon.js
146 ms
eaAJAX.js
150 ms
eacampaign.js
150 ms
typeahead.js
143 ms
jquery-1.7.2.min.js
231 ms
jquery-ui-1.8.17.custom.min.js
255 ms
jquery.en-1.1.js
203 ms
jquery.supersleight.js
186 ms
display-widgets-1.2.js
212 ms
scripts.js
469 ms
jquery.placeholder.js
480 ms
init.js
499 ms
action.retrievefile.do
124 ms
core.aurora.js
19888 ms
style.css
1275 ms
scripts.js
1428 ms
jquery.placeholder.js
847 ms
init.js
1068 ms
dc.js
55 ms
socialEngage.png
235 ms
pattern-lego-green.jpg
234 ms
more-info.png
232 ms
goto-home.png
233 ms
socialTwitter.png
200 ms
socialFacebook.png
330 ms
x.png
428 ms
gp_500_white.png
533 ms
splash.jpg
721 ms
jquery.min.js
43 ms
-g5pDUSRgvxvOl5u-a_WHw.woff
95 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
39 ms
HqHm7BVC_nzzTui2lzQTDaCWcynf_cDxXwCLxiixG1c.ttf
75 ms
bH7276GfdCjMjApa_dkG6T8E0i7KZn-EPnyo3HZu7kw.woff
99 ms
bH7276GfdCjMjApa_dkG6aCWcynf_cDxXwCLxiixG1c.ttf
98 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
99 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
98 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
99 ms
__utm.gif
72 ms
__utm.gif
79 ms
slide-2.jpg
225 ms
slide-3.jpg
227 ms
logo-greenpeace-white.png
419 ms
bg.jpg
217 ms
logo-save-artic.png
434 ms
logo-shell-lego.png
274 ms
sdk.js
105 ms
widgets.js
19 ms
analytics.js
45 ms
pattern-lego-red.jpg
166 ms
petition-bg-EN.png
186 ms
counter-EN.png
225 ms
collect
12 ms
slide-2.jpg
594 ms
slide-3.jpg
427 ms
64 ms
0sTQzbapM8j.js
101 ms
__utm.gif
10 ms
__utm.gif
10 ms
legoblockshell.org SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Legoblockshell.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Legoblockshell.org 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.
legoblockshell.org
Open Graph data is detected on the main page of Legoblockshell. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: