Access 1392.org. 인터넷 조정 - 사이버 조선왕조

1392.org screenshot

0

Performance
33

Accessibility

Visual factors better than
that of 18% of websites
75

Best Practices

More advanced features
available than in
35% of websites
75

SEO

Google-friendlier than
32% of websites

First Response

587 ms

Resources Loaded

7.7 sec

Page Rendered

254 ms

1392.org screenshot

About Website

Welcome to 1392.org homepage info - get ready to check 1392 best content right away, or after learning these important things about 1392.org

역사 기반 조선시대 인터넷 가상사회. 관직 제도, 과거 시험, 지역 활동 등

Visit 1392.org

Key Findings

We analyzed 1392.org page load time and found that the first response time was 587 ms and then it took 7.9 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)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

1392.org

587 ms

index.htm

211 ms

js

73 ms

1392lt.htm

209 ms

1392rt.htm

409 ms

Our browser made a total of 191 requests to load all elements on the main page. We found that 99% of them (190 requests) were addressed to the original 1392.org, 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain 1392.org.

Content Size

92.9 kB

After Optimization

84.1 kB

In fact, the total size of 1392.org main page is 92.9 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. 35% of websites need less resources to load. Images take 75.1 kB which makes up the majority of the site volume.

HTML Optimization

-58%

Potential reduce by 1.8 kB

Original 3.1 kB
After minification 3.1 kB
After compression 1.3 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 1.8 kB or 58% of the original size.

Image Optimization

-4%

Potential reduce by 2.9 kB

Original 75.1 kB
After minification 72.2 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. 1392 images are well optimized though.

JavaScript Optimization

-28%

Potential reduce by 4.1 kB

Original 14.7 kB
After minification 14.7 kB
After compression 10.6 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 4.1 kB or 28% of the original size.

Requests Now

187

After Optimization

105

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

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Browser errors were logged to the console

Search Engine Optimization Advices

Language and Encoding

Language Detected

KO
Language Claimed

N/A
Encoding

EUC-KR

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1392.org can be misinterpreted by Google and other search engines. Our service has detected that Korean 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 1392.org 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

1392.org

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