2.8 sec in total
414 ms
2.2 sec
218 ms
Visit worldbricks.com now to see the best up-to-date Worldbricks content for Germany and also check out these interesting facts you probably never knew about worldbricks.com
Laden Sie LEGO Bauanleitungen und Kataloge aus den 1950er Jahren bis in die Gegenwart. Suche nach Thema, Jahr oder Nummer.
Visit worldbricks.comWe analyzed Worldbricks.com page load time and found that the first response time was 414 ms and then it took 2.4 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.
worldbricks.com performance score
name
value
score
weighting
Value2.7 s
62/100
10%
Value4.2 s
45/100
25%
Value6.9 s
34/100
10%
Value2,040 ms
7/100
30%
Value0.032
100/100
15%
Value12.2 s
15/100
10%
414 ms
29 ms
20 ms
23 ms
69 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 43% of them (35 requests) were addressed to the original Worldbricks.com, 32% (26 requests) were made to Static.worldbricks.com and 6% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (778 ms) relates to the external source Static.worldbricks.com.
Page size can be reduced by 705.0 kB (56%)
1.3 MB
559.3 kB
In fact, the total size of Worldbricks.com 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. 70% of websites need less resources to load. Javascripts take 635.1 kB which makes up the majority of the site volume.
Potential reduce by 240.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 240.2 kB or 89% of the original size.
Potential reduce by 5.3 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. Worldbricks images are well optimized though.
Potential reduce by 398.1 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.1 kB or 63% of the original size.
Potential reduce by 61.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. Worldbricks.com needs all CSS files to be minified and compressed as it can save up to 61.3 kB or 86% of the original size.
Number of requests can be reduced by 35 (45%)
77
42
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Worldbricks. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
414 ms
gzip.php
29 ms
theme.css
20 ms
gzip.php
23 ms
maximenuck.php
69 ms
gzip.php
22 ms
template.css
21 ms
agorapro_latest.css
19 ms
jquery-1.8.3.min.js
17 ms
jquery-ui.min.js
20 ms
gzip.php
17 ms
gzip.php
18 ms
gzip.php
18 ms
gzip.php
21 ms
theme.js
20 ms
gzip.php
21 ms
gzip.php
21 ms
jquery.validate.min.js
22 ms
jquery.pwebcontact.min.js
20 ms
gzip.php
21 ms
gzip.php
22 ms
gzip.php
22 ms
adsbygoogle.js
9 ms
mon.js
36 ms
modalEffects.js
7 ms
uisearch.js
7 ms
css
23 ms
contact.jpg
78 ms
logo.png
506 ms
nl.gif
38 ms
de.gif
38 ms
fr.gif
38 ms
es.gif
38 ms
ru.gif
38 ms
it.gif
38 ms
en.gif
38 ms
logomob.png
463 ms
rss_icon.png
464 ms
001_m.jpg
464 ms
001_m.jpg
465 ms
001_m.jpg
465 ms
001_m.jpg
468 ms
001_m.jpg
539 ms
001_m.jpg
540 ms
001_m.jpg
540 ms
001_m.jpg
541 ms
388-taxi-station_m.jpg
536 ms
001_m.jpg
536 ms
001_m.jpg
541 ms
001_m.jpg
541 ms
001_m.jpg
601 ms
001_m.jpg
601 ms
001_m.jpg
600 ms
001_m.jpg
599 ms
avatar_3121.jpg
648 ms
avatar_1889.jpg
647 ms
avatar_1857.jpg
658 ms
76023-the-tumbler_120x120-c.jpg
685 ms
10538-fire-and-rescue-team_120x120-c.jpg
778 ms
21115-the-first-night_120x120-c.jpg
682 ms
40092-reindeer_120x120-c.jpg
724 ms
IcoMoon.woff
12 ms
ca-pub-0552221009199181.js
359 ms
zrt_lookup.html
358 ms
show_ads_impl.js
359 ms
sdk.js
391 ms
analytics.js
371 ms
_Incapsula_Resource
316 ms
ads
202 ms
fontawesome-webfont.woff
66 ms
osd.js
64 ms
collect
42 ms
_Incapsula_Resource
65 ms
collect
110 ms
ads
217 ms
251 ms
ads
155 ms
xd_arbiter.php
142 ms
xd_arbiter.php
266 ms
ads
229 ms
_Incapsula_Resource
50 ms
worldbricks.com 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
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
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
worldbricks.com 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
Page has valid source maps
worldbricks.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
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 doesn't use 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 Worldbricks.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 Worldbricks.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.
worldbricks.com
Open Graph description is not detected on the main page of Worldbricks. 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: