Access glowiz.com. (주)글로위즈

glowiz.com

705 ms

www.glowiz.co.kr

960 ms

chrome.png

1452 ms

NotoSansKR-Regular.woff

35 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that 25% of them (1 request) were addressed to the original Glowiz.com, 25% (1 request) were made to Glowiz.co.kr and 25% (1 request) were made to Storage.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Storage.googleapis.com.

Content Size

6.4 kB

After Optimization

5.8 kB

In fact, the total size of Glowiz.com main page is 6.4 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 5.6 kB which makes up the majority of the site volume.

HTML Optimization

-38%

Potential reduce by 283 B

Original 749 B
After minification 738 B
After compression 466 B

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 283 B or 38% of the original size.

Image Optimization

-5%

Potential reduce by 261 B

Original 5.6 kB
After minification 5.3 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. Glowiz images are well optimized though.

Requests Now

After Optimization

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Glowiz. According to our analytics all requests are already optimized.

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

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 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

Low

Ensure CSP is effective against XSS attacks

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

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 Glowiz.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 Glowiz.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

glowiz.com

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