Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

brickbrowse.com

Brick Browse | Shop LEGO®

Page Load Speed

3.2 sec in total

First Response

174 ms

Resources Loaded

2.7 sec

Page Rendered

345 ms

brickbrowse.com screenshot

About Website

Click here to check amazing Brick Browse content for Russia. Otherwise, check out these important facts you probably never knew about brickbrowse.com

Quickly and easily browse LEGO® sets, toys and products at Brick Browse.

Visit brickbrowse.com

Key Findings

We analyzed Brickbrowse.com page load time and found that the first response time was 174 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

brickbrowse.com performance score

0

Network Requests Diagram

brickbrowse.com

174 ms

www.brickbrowse.com

294 ms

cloudflare.min.js

26 ms

jquery.mobile-1.3.1.min.css

143 ms

combined.js

178 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 11% of them (10 requests) were addressed to the original Brickbrowse.com, 31% (28 requests) were made to Bb1.unoriginalmedia.com and 26% (23 requests) were made to Bb2.unoriginalmedia.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Bb1.unoriginalmedia.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 306.9 kB (33%)

Content Size

923.0 kB

After Optimization

616.0 kB

In fact, the total size of Brickbrowse.com main page is 923.0 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 426.7 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 52.2 kB

  • Original 71.2 kB
  • After minification 71.2 kB
  • After compression 18.9 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 52.2 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 5.0 kB

  • Original 426.7 kB
  • After minification 421.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. Brick Browse images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 168.7 kB

  • Original 330.8 kB
  • After minification 330.5 kB
  • After compression 162.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 168.7 kB or 51% of the original size.

CSS Optimization

-86%

Potential reduce by 81.0 kB

  • Original 94.3 kB
  • After minification 94.3 kB
  • After compression 13.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. Brickbrowse.com needs all CSS files to be minified and compressed as it can save up to 81.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (25%)

Requests Now

84

After Optimization

63

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

SEO Factors

brickbrowse.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brickbrowse.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Brickbrowse.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph data is detected on the main page of Brick Browse. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: