Access brickwiz.com. 레고 쇼핑몰 브릭위즈에 오신것을 진심으로 환영합니다. ^^

brickwiz.com screenshot

32

Performance

Renders faster than
52% of other websites
56

Accessibility

Visual factors better than
that of 24% of websites
67

Best Practices

More advanced features
available than in
24% of websites
84

SEO

Google-friendlier than
52% of websites

First Response

867 ms

Resources Loaded

8 sec

Page Rendered

516 ms

brickwiz.com screenshot

About Website

Click here to check amazing Brickwiz content for South Korea. Otherwise, check out these important facts you probably never knew about brickwiz.com

브릭위즈는 레고,Lego 제품,피규어,부품 및 레고호환 밀리터리 레고커스텀 밀리터리 호환 제품을 전문으로 취급하는 브릭 쇼핑몰입니다.

Visit brickwiz.com

Key Findings

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

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value16.6 s

0/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value190 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.544

13/100

15%

TTI (Time to Interactive)

Value27.6 s

0/100

10%

brickwiz.com

867 ms

common.css

392 ms

wcslog.js

8 ms

jquery-1.7.2.min.js

786 ms

lazyload.min.js

401 ms

Our browser made a total of 183 requests to load all elements on the main page. We found that 99% of them (182 requests) were addressed to the original Brickwiz.com, 1% (1 request) were made to Wcs.naver.net. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Brickwiz.com.

Content Size

2.6 MB

After Optimization

2.3 MB

In fact, the total size of Brickwiz.com main page is 2.6 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 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 151.8 kB

Original 176.9 kB
After minification 155.2 kB
After compression 25.1 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 21.7 kB, which is 12% 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 151.8 kB or 86% of the original size.

Image Optimization

-5%

Potential reduce by 105.7 kB

Original 2.2 MB
After minification 2.1 MB

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. Brickwiz images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 29.8 kB

Original 139.6 kB
After minification 138.1 kB
After compression 109.8 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 29.8 kB or 21% of the original size.

CSS Optimization

-38%

Potential reduce by 5.0 kB

Original 13.2 kB
After minification 12.8 kB
After compression 8.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. Brickwiz.com needs all CSS files to be minified and compressed as it can save up to 5.0 kB or 38% of the original size.

Requests Now

182

After Optimization

125

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

EUC-KR

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brickwiz.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 Brickwiz.com main page’s claimed encoding is euc-kr. 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

brickwiz.com

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