Tools & Wizards About Us
bricker.info screenshot

Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

bricker.info

Bricker - Informational site about Lego and other bricks

Page Load Speed

2.5 sec in total

First Response

502 ms

Resources Loaded

1.8 sec

Page Rendered

176 ms

bricker.info screenshot

About Website

Visit bricker.info now to see the best up-to-date Bricker content for United States and also check out these interesting facts you probably never knew about bricker.info

Construction sets-aggreator: LEGO sets, MEGABLOKS sets, minifigures, set reviews, catalogs.

Visit bricker.info

Key Findings

We analyzed Bricker.info page load time and found that the first response time was 502 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

bricker.info performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

51/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.19

64/100

15%

TTI (Time to Interactive)

Value5.5 s

70/100

10%

Network Requests Diagram

bricker.info

502 ms

style.css

570 ms

elastislide.css

469 ms

ru.png

187 ms

en.png

189 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 60% of them (38 requests) were addressed to the original Bricker.info, 27% (17 requests) were made to St.bricker.ru and 11% (7 requests) were made to I3.ytimg.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source St.bricker.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 411.4 kB (40%)

Content Size

1.0 MB

After Optimization

611.2 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Bricker.info main page is 1.0 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 622.2 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 337.9 kB

  • Original 372.9 kB
  • After minification 367.3 kB
  • After compression 35.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. 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 337.9 kB or 91% of the original size.

Image Optimization

-10%

Potential reduce by 65.1 kB

  • Original 622.2 kB
  • After minification 557.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. Bricker images are well optimized though.

CSS Optimization

-30%

Potential reduce by 8.4 kB

  • Original 27.6 kB
  • After minification 27.0 kB
  • After compression 19.2 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. Bricker.info needs all CSS files to be minified and compressed as it can save up to 8.4 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (28%)

Requests Now

61

After Optimization

44

  • Images
  • JavaScript
  • CSS

The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bricker. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

bricker.info

bricker.info

502 ms

style.css

style.css

570 ms

elastislide.css

elastislide.css

469 ms

ru.png

ru.png

187 ms

en.png

en.png

189 ms

fr.png

fr.png

190 ms

zh-tw.png

zh-tw.png

190 ms

pt.png

pt.png

198 ms

it.png

it.png

191 ms

de.png

de.png

282 ms

brk.png

brk.png

377 ms

search_cort.png

search_cort.png

378 ms

comment_navigation_cort.png

comment_navigation_cort.png

379 ms

key_g2.png

key_g2.png

382 ms

default.jpg

default.jpg

25 ms

jquery-1.11.2.min.js

jquery-1.11.2.min.js

288 ms

modernizr.custom.20190426.js

modernizr.custom.20190426.js

273 ms

jquerypp.custom.js

jquerypp.custom.js

397 ms

jquery.elastislide.js

jquery.elastislide.js

369 ms

jquery.swipebox.min.js

jquery.swipebox.min.js

396 ms

jquery.simplemodal145.js

jquery.simplemodal145.js

370 ms

script.js

script.js

372 ms

searchsuggest.js

searchsuggest.js

382 ms

js

js

59 ms

21350.jpg

21350.jpg

634 ms

40748.jpg

40748.jpg

600 ms

40706.jpg

40706.jpg

601 ms

40705.jpg

40705.jpg

647 ms

42184.jpg

42184.jpg

650 ms

main.jpg

main.jpg

697 ms

main.jpg

main.jpg

934 ms

main.jpg

main.jpg

600 ms

main.jpg

main.jpg

955 ms

main.jpg

main.jpg

744 ms

75385_main.jpg

75385_main.jpg

749 ms

60421_main.jpg

60421_main.jpg

760 ms

76923_main.jpg

76923_main.jpg

800 ms

40690_main.jpg

40690_main.jpg

847 ms

43244_main.jpg

43244_main.jpg

853 ms

bl.gif

bl.gif

855 ms

9741d_phpYpBNVv.jpeg

9741d_phpYpBNVv.jpeg

387 ms

6139f_LEGO_40748_Prod.png

6139f_LEGO_40748_Prod.png

643 ms

1a941_LEGO_40706_Prod.png

1a941_LEGO_40706_Prod.png

644 ms

ac9b4_LEGO_40705_Prod.png

ac9b4_LEGO_40705_Prod.png

446 ms

1cafc_LEGO_42184_Prod.png

1cafc_LEGO_42184_Prod.png

643 ms

IMGP7558.jpg

IMGP7558.jpg

1024 ms

LEGO_60265-55.jpg

LEGO_60265-55.jpg

952 ms

LEGO_60191-04.jpg

LEGO_60191-04.jpg

1118 ms

be395_phpENcwDE

be395_phpENcwDE

927 ms

photo-000.jpg

photo-000.jpg

1128 ms

default.jpg

default.jpg

23 ms

default.jpg

default.jpg

35 ms

default.jpg

default.jpg

23 ms

default.jpg

default.jpg

27 ms

default.jpg

default.jpg

25 ms

default.jpg

default.jpg

28 ms

mecabricks.gif

mecabricks.gif

893 ms

brickpicker_logo.gif

brickpicker_logo.gif

864 ms

box.png

box.png

174 ms

hbricks.png

hbricks.png

268 ms

dbrick7.png

dbrick7.png

364 ms

1024.css

1024.css

96 ms

small-device.css

small-device.css

97 ms

Accessibility Review

bricker.info accessibility score

80

Accessibility Issues

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

bricker.info best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

bricker.info SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Document doesn't have a valid hreflang

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bricker.info 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 Bricker.info 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.

Social Sharing Optimization

bricker.info

Open Graph description is not detected on the main page of Bricker. 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: