2.7 sec in total
174 ms
1.5 sec
997 ms
Welcome to thebrickfan.com homepage info - get ready to check The Brick Fan best content for United States right away, or after learning these important things about thebrickfan.com
LEGO News, LEGO Reviews, and Discussions
Visit thebrickfan.comWe analyzed Thebrickfan.com page load time and found that the first response time was 174 ms and then it took 2.5 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.
thebrickfan.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value7.6 s
3/100
25%
Value14.8 s
1/100
10%
Value1,200 ms
21/100
30%
Value0.012
100/100
15%
Value26.1 s
0/100
10%
174 ms
299 ms
222 ms
37 ms
36 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 26% of them (27 requests) were addressed to the original Thebrickfan.com, 5% (5 requests) were made to Pagead2.googlesyndication.com and 5% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (788 ms) relates to the external source Brickbuilderspro.com.
Page size can be reduced by 825.7 kB (25%)
3.3 MB
2.5 MB
In fact, the total size of Thebrickfan.com main page is 3.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. 75% 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. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 58.4 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 58.4 kB or 78% of the original size.
Potential reduce by 153.8 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. The Brick Fan images are well optimized though.
Potential reduce by 363.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 363.4 kB or 63% of the original size.
Potential reduce by 250.0 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. Thebrickfan.com needs all CSS files to be minified and compressed as it can save up to 250.0 kB or 82% of the original size.
Number of requests can be reduced by 52 (55%)
95
43
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of The Brick Fan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
thebrickfan.com
174 ms
www.thebrickfan.com
299 ms
plusone.js
222 ms
1456746732index.css
37 ms
1456746733index.js
36 ms
1456746732index.css
36 ms
buttons.js
35 ms
show_ads.js
6 ms
brand
262 ms
wp-emoji-release.min.js
127 ms
ga.js
181 ms
ca-pub-0069905765356104.js
292 ms
zrt_lookup.html
298 ms
show_ads_impl.js
141 ms
XJLDovX.png
645 ms
24463429172_aeeb05e6c9.jpg
670 ms
3XJpnsQdAQM
350 ms
1677332-o_1970rm4mkkr7lrdskd1ohd15atc-full.JPG
640 ms
SdmDb8ozcXc
641 ms
Halloween-new-set-2016.jpeg
237 ms
BrickbuildersproGIF.gif
788 ms
q
108 ms
9169743_orig.jpg
334 ms
24815041249_88f3e08dfe.jpg
657 ms
24633867883_4e40f34630.jpg
753 ms
25167648701_459a33a702.jpg
656 ms
light-gradient_003750223.jpg
272 ms
thebrickfan2.png
70 ms
sidebarbg.png
70 ms
mainbg.png
71 ms
comments.png
70 ms
lego-oscars-2016.png
332 ms
facebook2.gif
123 ms
twitter.gif
124 ms
googleplus1.png
189 ms
googleplus2.gif
189 ms
Instagram.gif
270 ms
rss.gif
269 ms
Brick-Fest-MD-200x200.jpg
280 ms
BrickShowShop.jpg
268 ms
banner_200x200_brickclassifieds_updated.jpg
303 ms
LEGO_logo_125x125.gif
261 ms
show
250 ms
font-awesome.min.css
206 ms
1456746737index.css
285 ms
wp-embed.min.js
309 ms
other-shortcodes.js
294 ms
amazon.js
293 ms
amazon.jpg
309 ms
amazon-warehouse.png
308 ms
a-logo-amazon.png
189 ms
61TrXTglmkL._AC_SR98,95_.jpg
234 ms
ir
216 ms
json
216 ms
prime.png
170 ms
cart.gif
168 ms
cb=gapi.loaded_0
167 ms
ads
451 ms
google_custom_search_watermark.gif
432 ms
__utm.gif
422 ms
osd.js
96 ms
__utm.gif
431 ms
ads
386 ms
count.js
381 ms
counter.js
92 ms
ads
368 ms
www-embed-player-vflQrT_sR.css
370 ms
www-embed-player.js
392 ms
base.js
464 ms
t.php
440 ms
quant.js
268 ms
getAllAppDefault.esi
158 ms
fontawesome-webfont.woff
30 ms
ads.js
156 ms
m_js_controller.js
39 ms
abg.js
55 ms
count-data.js
23 ms
pixel;r=277916493;a=p-p1CaCJ3cEcKQE;fpan=1;fpa=P0-1045697869-1456802416848;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456802416847;tzo=-180;ref=;url=http%3A%2F%2Fwww.thebrickfan.com%2F;ogl=locale.en_US%2Ctype.website%2Ctitle.The%20Brick%20Fan%20-%20LEGO%20News%252C%20LEGO%20Reviews%252C%20and%20Discussions%2Cdescription.A%20LEGO%20blog%20dedicated%20to%20reporting%20the%20latest%20LEGO%20news%20and%20information%252E%20We%20also%2Curl.http%3A%2F%2Fwww%252Ethebrickfan%252Ecom%2Csite_name.The%20Brick%20Fan
16 ms
favicon
109 ms
googlelogo_color_112x36dp.png
107 ms
nessie_icon_tiamat_white.png
49 ms
s
61 ms
x_button_blue2.png
50 ms
getSegment.php
36 ms
checkOAuth.esi
113 ms
New%20folder_56_VS-CODE_728x90_A.jpg
155 ms
ddcssl.htm
203 ms
t.dhj
90 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
88 ms
1eJU4PjErWSV5LNTKFXcze5UHikZLg3viIH581vcHWA.js
29 ms
ad_status.js
78 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
73 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
84 ms
t.dhj
33 ms
cm
45 ms
s-3271.xgi
17 ms
11 ms
hbpix
97 ms
12 ms
pixel
71 ms
pixel
41 ms
xrefid.xgi
13 ms
2981
33 ms
thebrickfan.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.
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
Image elements do not have [alt] attributes
thebrickfan.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
thebrickfan.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Thebrickfan.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 Thebrickfan.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.
thebrickfan.com
Open Graph data is detected on the main page of The Brick Fan. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: