787 ms in total
90 ms
305 ms
392 ms
Welcome to brickfair.com homepage info - get ready to check Brick Fair best content for United States right away, or after learning these important things about brickfair.com
North America's premiere LEGO fan convention and expo.
Visit brickfair.comWe analyzed Brickfair.com page load time and found that the first response time was 90 ms and then it took 697 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
brickfair.com performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value12.1 s
0/100
25%
Value5.3 s
58/100
10%
Value290 ms
79/100
30%
Value0.012
100/100
15%
Value12.5 s
14/100
10%
90 ms
64 ms
13 ms
9 ms
22 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that all of those requests were addressed to Brickfair.com and no external sources were called. The less responsive or slowest element that took the longest time to load (90 ms) belongs to the original domain Brickfair.com.
Page size can be reduced by 979.5 kB (44%)
2.2 MB
1.3 MB
In fact, the total size of Brickfair.com main page is 2.2 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. 40% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 8.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. This page needs HTML code to be minified as it can gain 2.1 kB, which is 20% 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 8.2 kB or 75% of the original size.
Potential reduce by 870.7 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. Obviously, Brick Fair needs image optimization as it can save up to 870.7 kB or 41% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 45.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 45.0 kB or 83% of the original size.
Potential reduce by 55.6 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. Brickfair.com needs all CSS files to be minified and compressed as it can save up to 55.6 kB or 87% of the original size.
Number of requests can be reduced by 3 (8%)
40
37
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brick Fair. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for CSS and as a result speed up the page load time.
brickfair.com
90 ms
www.brickfair.com
64 ms
BrickFairStylesheet.css
13 ms
Stylesheet.css
9 ms
BFJavascript.js
22 ms
Snowfall.js
16 ms
BrickyBG20.png
11 ms
Cursor-Green.png
10 ms
Bricks.png
13 ms
Cursor-Blue.png
11 ms
Pointer-Yellow.png
11 ms
SiteName.png
21 ms
YellowBricks.png
32 ms
1x1sColored.gif
10 ms
Facebook.png
12 ms
Twitter.png
14 ms
MailingList.png
16 ms
NoStrollers.png
17 ms
Hollow2x4.png
22 ms
GatesOpen.jpg
23 ms
GetTickets.jpg
69 ms
ThingsToSee.png
20 ms
Vity-Train.jpg
33 ms
Vity-StarWars.jpg
28 ms
Vity-GBC.jpg
32 ms
Vity-Bionicle.jpg
44 ms
Vity-Military.jpg
32 ms
Vity-City.jpg
71 ms
Vity-PopCulture.jpg
40 ms
Vity-Mindstorms.jpg
41 ms
ThingsToDo.png
39 ms
Vity-Bingo.jpg
52 ms
Vity-Play.jpg
50 ms
Vity-Guess.jpg
46 ms
Vity-Photo.jpg
61 ms
Vity-Bounce.jpg
57 ms
Vity-Shop.jpg
61 ms
Vity-Race.jpg
68 ms
Vity-Game.jpg
69 ms
Tower.jpg
70 ms
BrickFairStylesheet-Print.css
6 ms
BrickFairStylesheet-Phone.css
7 ms
brickfair.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
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.
brickfair.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
brickfair.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 Brickfair.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 Brickfair.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.
brickfair.com
Open Graph description is not detected on the main page of Brick Fair. 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: