Tools & Wizards About Us
whoiscall.net screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

whoiscall.net

후이즈콜(WhoisCall)

Page Load Speed

15.8 sec in total

First Response

3 sec

Resources Loaded

12.7 sec

Page Rendered

90 ms

whoiscall.net screenshot

About Website

Visit whoiscall.net now to see the best up-to-date Whois Call content for South Korea and also check out these interesting facts you probably never knew about whoiscall.net

광고, 스팸 전화는 이제 그만!! 후이즈콜(WhoisCall)은 빅데이터를 기반으로 발신자의 정보를 알려주는 전화번호검색 서비스

Visit whoiscall.net

Key Findings

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

Performance Metrics

whoiscall.net performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

51/100

25%

SI (Speed Index)

Value18.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,670 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.5 s

11/100

10%

Network Requests Diagram

whoiscall.net

3026 ms

whoiscall.net

1410 ms

basic.css

185 ms

adsbygoogle.js

111 ms

wcslog.js

70 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 77% of them (10 requests) were addressed to the original Whoiscall.net, 15% (2 requests) were made to Pagead2.googlesyndication.com and 8% (1 request) were made to Wcs.naver.net. The less responsive or slowest element that took the longest time to load (7.8 sec) belongs to the original domain Whoiscall.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 163.8 kB (38%)

Content Size

425.9 kB

After Optimization

262.1 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Whoiscall.net main page is 425.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 5% of websites need less resources to load. Javascripts take 399.7 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 11.8 kB

  • Original 15.8 kB
  • After minification 14.7 kB
  • After compression 4.0 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 11.8 kB or 75% of the original size.

JavaScript Optimization

-37%

Potential reduce by 147.0 kB

  • Original 399.7 kB
  • After minification 399.7 kB
  • After compression 252.7 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 147.0 kB or 37% of the original size.

CSS Optimization

-48%

Potential reduce by 5.0 kB

  • Original 10.4 kB
  • After minification 10.2 kB
  • After compression 5.3 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. Whoiscall.net needs all CSS files to be minified and compressed as it can save up to 5.0 kB or 48% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (36%)

Requests Now

11

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whoiscall.net

whoiscall.net

3026 ms

whoiscall.net

whoiscall.net

1410 ms

basic.css

basic.css

185 ms

adsbygoogle.js

adsbygoogle.js

111 ms

wcslog.js

wcslog.js

70 ms

logo.gif

logo.gif

369 ms

common.css

common.css

7773 ms

layout.css

layout.css

1729 ms

table.css

table.css

2300 ms

page_style.css

page_style.css

1944 ms

show_ads_impl.js

show_ads_impl.js

252 ms

bg_body.gif

bg_body.gif

184 ms

txt.gif

txt.gif

199 ms

Accessibility Review

whoiscall.net accessibility score

77

Accessibility Issues

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

Image elements do not have [alt] attributes

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

whoiscall.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Page has valid source maps

SEO Factors

whoiscall.net SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

whoiscall.net

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: