4.8 sec in total
1.2 sec
2.7 sec
931 ms
Welcome to brickswag.com homepage info - get ready to check Brickswag best content for United States right away, or after learning these important things about brickswag.com
#1 Club for LEGO Fans
Visit brickswag.comWe analyzed Brickswag.com page load time and found that the first response time was 1.2 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
brickswag.com performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value3.7 s
58/100
25%
Value2.9 s
95/100
10%
Value360 ms
71/100
30%
Value0.099
90/100
15%
Value3.9 s
88/100
10%
1155 ms
74 ms
75 ms
78 ms
79 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 62% of them (54 requests) were addressed to the original Brickswag.com, 5% (4 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Pixel-geo.prfct.co. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Brickswag.com.
Page size can be reduced by 1.2 MB (27%)
4.7 MB
3.4 MB
In fact, the total size of Brickswag.com main page is 4.7 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. 65% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 46.6 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 46.6 kB or 79% of the original size.
Potential reduce by 2.9 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. Brickswag images are well optimized though.
Potential reduce by 240.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 240.0 kB or 70% of the original size.
Potential reduce by 958.1 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. Brickswag.com needs all CSS files to be minified and compressed as it can save up to 958.1 kB or 91% of the original size.
Number of requests can be reduced by 55 (69%)
80
25
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brickswag. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
brickswag.com
1155 ms
wp-emoji-release.min.js
74 ms
admin_icon.min.css
75 ms
style.css
78 ms
styles.css
79 ms
soon.min.css
98 ms
css
24 ms
casper-style.css
109 ms
font-awesome.min.css
139 ms
js_composer.css
234 ms
style.min.css
136 ms
Defaults.css
158 ms
jquery.js
223 ms
jquery-migrate.min.js
201 ms
typekit.js
232 ms
header-scroll.js
283 ms
api.min.js
7 ms
core.css
210 ms
header-image.css
209 ms
visual-composer.css
217 ms
CKJS4.js
143 ms
font-awesome.min.css
120 ms
tooltipster.css
185 ms
lightbox.css
246 ms
style.css
250 ms
background-style.min.css
249 ms
cfpop.js
244 ms
jquery.form.min.js
247 ms
scripts.js
247 ms
soon.min.js
248 ms
responsive-menu.js
253 ms
js_composer_front.js
251 ms
jquery.tooltipster.min.js
253 ms
lightbox.js
252 ms
init.min.js
253 ms
jquery-appear.min.js
253 ms
ultimate_bg.min.js
257 ms
custom.min.js
254 ms
home-path.png
450 ms
yellow-bg.jpg
450 ms
logo@2x.png
82 ms
top-bg.jpg
85 ms
products.png
826 ms
robot-white.png
171 ms
dk.png
111 ms
lego.png
111 ms
marvel.png
112 ms
starwars.png
114 ms
brickwarriors.png
177 ms
circle-11.png
179 ms
circle-21.png
179 ms
circle-31.png
441 ms
robot-black.png
177 ms
arrow-down.png
442 ms
pack11.jpg
441 ms
pack21.jpg
442 ms
pack31.jpg
444 ms
sweet.png
443 ms
pack41.jpg
443 ms
OctoberBox.png
1340 ms
APH4jr0uSos5wiut5cpjronF5uFdDttMLvmWuJdhhgs.ttf
29 ms
webfont.js
29 ms
jquery.min.js
336 ms
fbevents.js
26 ms
gtm.js
273 ms
5590887f5e7c98009d00004d.js
273 ms
css
22 ms
264 ms
231984
182 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
29 ms
webfont.js
52 ms
tagjs
179 ms
css
123 ms
1c614d46f2861446138515-BrickBotHead.png
255 ms
arrow.png
239 ms
70 ms
adsct
205 ms
Pug
179 ms
cb
79 ms
ncm
20 ms
cb
12 ms
tap.php
37 ms
sd
42 ms
close.png
34 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
14 ms
LQ7WLTaITDg4OSRuOZCpsy3USBnSvpkopQaUR-2r7iU.ttf
37 ms
cb
3 ms
brickswag.com accessibility score
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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
brickswag.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
Page has valid source maps
brickswag.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brickswag.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Brickswag.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.
brickswag.com
Open Graph description is not detected on the main page of Brickswag. 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: