Access attopangea.com. 팀벅2

Report Summary

attopangea.com

689 ms

timbuk2

1301 ms

sp_u_skip.png

279 ms

arrow_down_gray_5x3.svg

269 ms

notice_error_75x67.svg

269 ms

Our browser made a total of 6 requests to load all elements on the main page. We found that 17% of them (1 request) were addressed to the original Attopangea.com, 50% (3 requests) were made to Img.shop.naver.net and 17% (1 request) were made to Smartstore.naver.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Smartstore.naver.com.

Content Size

1.6 kB

After Optimization

1.3 kB

In fact, the total size of Attopangea.com main page is 1.6 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 967 B which makes up the majority of the site volume.

HTML Optimization

-40%

Potential reduce by 255 B

Original 644 B
After minification 633 B
After compression 389 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 255 B or 40% of the original size.

Image Optimization

-1%

Potential reduce by 12 B

Original 967 B
After minification 955 B

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

Requests Now

After Optimization

The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Attopangea. 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

Issues were logged in the Issues panel in Chrome Devtools

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

N/A
Language Claimed

N/A
Encoding

EUC-KR

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Attopangea.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Attopangea.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

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