Tools & Wizards About Us
jongmyo.net screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

jongmyo.net

종묘대제

Page Load Speed

4.9 sec in total

First Response

1.2 sec

Resources Loaded

3.6 sec

Page Rendered

134 ms

jongmyo.net screenshot

About Website

Visit jongmyo.net now to see the best up-to-date Jongmyo content and also check out these interesting facts you probably never knew about jongmyo.net

국가무형문화재 제56호 종묘대제

Visit jongmyo.net

Key Findings

We analyzed Jongmyo.net page load time and found that the first response time was 1.2 sec and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

jongmyo.net performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value960 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value1.011

2/100

15%

TTI (Time to Interactive)

Value14.5 s

9/100

10%

Network Requests Diagram

jongmyo.net

1178 ms

style.css

457 ms

banner_search.gif

205 ms

button_home.gif

234 ms

button_sitemap.gif

401 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that all of those requests were addressed to Jongmyo.net and no external sources were called. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Jongmyo.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 17.1 kB (82%)

Content Size

20.9 kB

After Optimization

3.8 kB

  • HTML
  • CSS

In fact, the total size of Jongmyo.net main page is 20.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. Only 10% of websites need less resources to load. HTML takes 19.7 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 16.2 kB

  • Original 19.7 kB
  • After minification 16.4 kB
  • After compression 3.5 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 3.3 kB, which is 17% 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 16.2 kB or 82% of the original size.

CSS Optimization

-73%

Potential reduce by 932 B

  • Original 1.3 kB
  • After minification 1.1 kB
  • After compression 343 B

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. Jongmyo.net needs all CSS files to be minified and compressed as it can save up to 932 B or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (23%)

Requests Now

40

After Optimization

31

  • Images
  • CSS

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

Network Requests Diagram

jongmyo.net

jongmyo.net

1178 ms

style.css

style.css

457 ms

banner_search.gif

banner_search.gif

205 ms

button_home.gif

button_home.gif

234 ms

button_sitemap.gif

button_sitemap.gif

401 ms

button_notice.gif

button_notice.gif

402 ms

button_email.gif

button_email.gif

453 ms

button_brochure.gif

button_brochure.gif

461 ms

logo.gif

logo.gif

934 ms

copyright.gif

copyright.gif

760 ms

button_member.gif

button_member.gif

597 ms

dot01.gif

dot01.gif

598 ms

button_id_pw.gif

button_id_pw.gif

675 ms

text_id.gif

text_id.gif

688 ms

text_pw.gif

text_pw.gif

793 ms

button_login.gif

button_login.gif

796 ms

process01.gif

process01.gif

1374 ms

process02.gif

process02.gif

1152 ms

process03.gif

process03.gif

1314 ms

music.gif

music.gif

1231 ms

palilmu.gif

palilmu.gif

1012 ms

clothes.gif

clothes.gif

1180 ms

jegi.gif

jegi.gif

1231 ms

notice.gif

notice.gif

1389 ms

icon01.gif

icon01.gif

1410 ms

icon_more01.gif

icon_more01.gif

1426 ms

data.gif

data.gif

1436 ms

icon02.gif

icon02.gif

1564 ms

icon_more02.gif

icon_more02.gif

1593 ms

origin.gif

origin.gif

1632 ms

imgz_mov.gif

imgz_mov.gif

1675 ms

banner01.gif

banner01.gif

1648 ms

banner02.gif

banner02.gif

1650 ms

banner03.gif

banner03.gif

1822 ms

banner04.gif

banner04.gif

1815 ms

right.gif

right.gif

1863 ms

right02.gif

right02.gif

1844 ms

top.gif

top.gif

1857 ms

bg.gif

bg.gif

1731 ms

bg02.gif

bg02.gif

2080 ms

right_bg.gif

right_bg.gif

1693 ms

Accessibility Review

jongmyo.net accessibility score

74

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

jongmyo.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

jongmyo.net SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

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 Jongmyo.net 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 Jongmyo.net 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

jongmyo.net

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