1.2 sec in total
113 ms
507 ms
623 ms
Welcome to brickeconomy.com homepage info - get ready to check Brick Economy best content for United States right away, or after learning these important things about brickeconomy.com
A comprehensive guide to LEGO economics, market values, worth and trends. What is your LEGO worth? BrickEconomy will know.
Visit brickeconomy.comWe analyzed Brickeconomy.com page load time and found that the first response time was 113 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
brickeconomy.com performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value4.3 s
42/100
25%
Value7.5 s
26/100
10%
Value2,300 ms
5/100
30%
Value0.003
100/100
15%
Value22.0 s
1/100
10%
113 ms
29 ms
25 ms
24 ms
27 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 95% of them (77 requests) were addressed to the original Brickeconomy.com, 1% (1 request) were made to Ajax.googleapis.com and 1% (1 request) were made to Cdn.fuseplatform.net. The less responsive or slowest element that took the longest time to load (290 ms) relates to the external source Cdn.fuseplatform.net.
Page size can be reduced by 215.9 kB (25%)
857.4 kB
641.5 kB
In fact, the total size of Brickeconomy.com main page is 857.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 413.7 kB which makes up the majority of the site volume.
Potential reduce by 178.0 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 43.3 kB, which is 21% 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 178.0 kB or 88% of the original size.
Potential reduce by 12.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. Brick Economy images are well optimized though.
Potential reduce by 8.4 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. This website has mostly compressed JavaScripts.
Potential reduce by 17.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. Brickeconomy.com needs all CSS files to be minified and compressed as it can save up to 17.3 kB or 23% of the original size.
Number of requests can be reduced by 11 (14%)
80
69
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brick Economy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
www.brickeconomy.com
113 ms
jquery.min.js
29 ms
bootstrap.min.css
25 ms
styles.css
24 ms
js.js
27 ms
fuse.js
290 ms
js
154 ms
WebResource.axd
57 ms
ScriptResource.axd
58 ms
ScriptResource.axd
63 ms
WebResource.axd
67 ms
bootstrap.min.js
58 ms
jquery.autocomplete.js
58 ms
bootstrap-notify.min.js
59 ms
animate.min.css
112 ms
v84a3a4012de94ce1a686ba8c167c359c1696973893317
192 ms
flag-us.png
103 ms
graph-value-over-time.png
105 ms
graph-estimated-value-over-time.png
107 ms
graph-sales-trends-over-time.png
106 ms
lego-75313-1_medium.jpg
103 ms
lego-42111-1_medium.jpg
105 ms
lego-75292-1_medium.jpg
146 ms
lego-10269-1_medium.jpg
179 ms
lego-75953-1_medium.jpg
179 ms
lego-75888-1_medium.jpg
178 ms
lego-41611-1_medium.jpg
145 ms
lego-41615-1_medium.jpg
145 ms
lego-41613-1_medium.jpg
179 ms
lego-75192-1_medium.jpg
180 ms
lego-21034-1_medium.jpg
182 ms
lego-75878-1_medium.jpg
183 ms
lego-10251-1_medium.jpg
181 ms
lego-21029-1_medium.jpg
180 ms
lego-21307-1_medium.jpg
184 ms
lego-41572-1_medium.jpg
183 ms
lego-41063-1_medium.jpg
186 ms
lego-75911-1_medium.jpg
184 ms
lego-42023-1_medium.jpg
189 ms
lego-44021-1_medium.jpg
185 ms
lego-60018-1_medium.jpg
187 ms
lego-5886-1_medium.jpg
188 ms
lego-5885-1_medium.jpg
189 ms
lego-4530-1_medium.jpg
186 ms
lego-10221-1_medium.jpg
219 ms
lego-4184-1_medium.jpg
217 ms
lego-2282-1_medium.jpg
217 ms
lego-2068-1_medium.jpg
218 ms
lego-10212-1_medium.jpg
220 ms
lego-10211-1_medium.jpg
165 ms
lego-8039-1_medium.jpg
136 ms
lego-8274-1_medium.jpg
135 ms
icon96_beminifig_1.png
130 ms
lego-910030-1_medium.jpg
186 ms
lego-910031-1_medium.jpg
129 ms
lego-910032-1_medium.jpg
131 ms
lego-910029-1_medium.jpg
128 ms
lego-910033-1_medium.jpg
126 ms
lego-40714-1_medium.jpg
90 ms
lego-31158-1_medium.jpg
92 ms
lego-30677-1_medium.jpg
63 ms
lego-71813-1_medium.jpg
60 ms
lego-40677-1_medium.jpg
60 ms
lego-41809-1_medium.jpg
60 ms
lego-40625-1_medium.jpg
59 ms
lego-76410-1_medium.jpg
60 ms
lego-76911-1_medium.jpg
60 ms
lego-76912-1_medium.jpg
60 ms
lego-76412-1_medium.jpg
58 ms
lego-21337-1_medium.jpg
59 ms
lego-76220-1_medium.jpg
58 ms
lego-21028-1_medium.jpg
58 ms
lego-10713-1_medium.jpg
58 ms
lego-21042-1_medium.jpg
58 ms
lego-40384-1_medium.jpg
59 ms
lego-80008-1_medium.jpg
56 ms
lego-45028-1_medium.jpg
57 ms
lego-40461-1_medium.jpg
56 ms
lego-40477-1_medium.jpg
57 ms
lego-75309-1_medium.jpg
40 ms
logo-header-2x.png
40 ms
brickeconomy.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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>).
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.
brickeconomy.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
brickeconomy.com 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
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 Brickeconomy.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 Brickeconomy.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.
brickeconomy.com
Open Graph description is not detected on the main page of Brick Economy. 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: