Tools & Wizards About Us
land.naver.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

land.naver.com

네이버페이 부동산

Page Load Speed

4.2 sec in total

First Response

1.1 sec

Resources Loaded

3 sec

Page Rendered

133 ms

land.naver.com screenshot

About Website

Click here to check amazing Land Naver content for South Korea. Otherwise, check out these important facts you probably never knew about land.naver.com

내 집 마련의 시작, 네이버페이 부동산

Visit land.naver.com

Key Findings

We analyzed Land.naver.com page load time and found that the first response time was 1.1 sec and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

land.naver.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value14.6 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value1,700 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.095

91/100

15%

TTI (Time to Interactive)

Value15.6 s

6/100

10%

Network Requests Diagram

land.naver.com

1095 ms

land_home.css

82 ms

lcslog.js

80 ms

gfp-core.js

91 ms

wcslog.js

69 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Land.naver.com, 63% (33 requests) were made to Ssl.pstatic.net and 19% (10 requests) were made to Landthumb-phinf.pstatic.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Land.naver.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 858.6 kB (43%)

Content Size

2.0 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Land.naver.com main page is 2.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 117.3 kB

  • Original 148.1 kB
  • After minification 138.7 kB
  • After compression 30.8 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 117.3 kB or 79% of the original size.

Image Optimization

-10%

Potential reduce by 54.1 kB

  • Original 541.6 kB
  • After minification 487.4 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. Land Naver images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 686.9 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 586.2 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 686.9 kB or 54% of the original size.

CSS Optimization

-1%

Potential reduce by 218 B

  • Original 18.3 kB
  • After minification 18.3 kB
  • After compression 18.0 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. Land.naver.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 20 (41%)

Requests Now

49

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

land.naver.com

land.naver.com

1095 ms

land_home.css

land_home.css

82 ms

lcslog.js

lcslog.js

80 ms

gfp-core.js

gfp-core.js

91 ms

wcslog.js

wcslog.js

69 ms

gnb_utf8.nhn

gnb_utf8.nhn

129 ms

jquery.min.js

jquery.min.js

152 ms

swiper-bundle.min.css

swiper-bundle.min.css

74 ms

swiper-bundle.min.js

swiper-bundle.min.js

151 ms

photoinfra_1714639244655.jpg

photoinfra_1714639244655.jpg

418 ms

photoinfra_1713504133753.jpg

photoinfra_1713504133753.jpg

420 ms

photoinfra_1714441008588.jpg

photoinfra_1714441008588.jpg

425 ms

%B1%DD%C8%A3_%BE%DF%C5%BE_%B1%D7%B8%B0%C6%C4%C5%A9.png

%B1%DD%C8%A3_%BE%DF%C5%BE_%B1%D7%B8%B0%C6%C4%C5%A9.png

426 ms

%B9%DD%C1%B6%B0%A8%B5%B5.jpg

%B9%DD%C1%B6%B0%A8%B5%B5.jpg

424 ms

%B5%CE%BB%EA%B0%C7%BC%B3_%BF%EB%C0%CE_%C1%B6%B0%A8%B5%B5.png

%B5%CE%BB%EA%B0%C7%BC%B3_%BF%EB%C0%CE_%C1%B6%B0%A8%B5%B5.png

425 ms

2_%C5%F5%BD%C3%B5%B5.png

2_%C5%F5%BD%C3%B5%B5.png

423 ms

%B4%EB%C7%A5%BD%E6%B3%D7%C0%CF.png

%B4%EB%C7%A5%BD%E6%B3%D7%C0%CF.png

428 ms

%B0%AD%B8%AA%BE%C6%C0%CC%C6%C4%C5%A9_%C1%B6%B0%A8%B5%B5_%B9%D9%B4%D9.png

%B0%AD%B8%AA%BE%C6%C0%CC%C6%C4%C5%A9_%C1%B6%B0%A8%B5%B5_%B9%D9%B4%D9.png

427 ms

%C7%D8%B8%B5%C5%CF_%B8%B6%B7%B9_%B9%DD%C1%B6%B0%A8%B5%B5.png

%C7%D8%B8%B5%C5%CF_%B8%B6%B7%B9_%B9%DD%C1%B6%B0%A8%B5%B5.png

427 ms

sp_u_skip.png

sp_u_skip.png

87 ms

guarantee_banner4.png

guarantee_banner4.png

88 ms

gfp-sdk.js

gfp-sdk.js

75 ms

m

m

180 ms

promo_npay_2309.png

promo_npay_2309.png

80 ms

sp_home.png

sp_home.png

81 ms

sp_gnb_one.png

sp_gnb_one.png

81 ms

bg_map_top3_181105.png

bg_map_top3_181105.png

58 ms

bg_home_con2.gif

bg_home_con2.gif

60 ms

bu_arrow2.gif

bu_arrow2.gif

57 ms

bu_dot.gif

bu_dot.gif

58 ms

sp_homebeta.png

sp_homebeta.png

59 ms

sp_usefultip.png

sp_usefultip.png

58 ms

cs_ops_webncc.js

cs_ops_webncc.js

10 ms

home_jindo.min.js

home_jindo.min.js

68 ms

home_page.min.js

home_page.min.js

65 ms

land.html5.flash.js

land.html5.flash.js

69 ms

guarantee_QR.jpg

guarantee_QR.jpg

66 ms

bg_header_footer.gif

bg_header_footer.gif

56 ms

bu_bar.gif

bu_bar.gif

55 ms

logo_financial.png

logo_financial.png

55 ms

Land_html5_atlas_1.png

Land_html5_atlas_1.png

127 ms

airsList.naver

airsList.naver

325 ms

call

call

511 ms

NanumSquareB.woff

NanumSquareB.woff

57 ms

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

6 ms

1100000000_large.js

1100000000_large.js

62 ms

1100000000_large_atlas_1.png

1100000000_large_atlas_1.png

153 ms

getLoginStatus

getLoginStatus

833 ms

splugin.js

splugin.js

71 ms

spi_layer_https.css

spi_layer_https.css

24 ms

gfp-ext-nda.js

gfp-ext-nda.js

8 ms

sf-ext.js

sf-ext.js

9 ms

Accessibility Review

land.naver.com accessibility score

88

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

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

land.naver.com best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

land.naver.com SEO score

86

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

High

Page is blocked from indexing

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

    KO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Land.naver.com can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Land.naver.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

land.naver.com

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