Tools & Wizards About Us
whoiscaller.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

whoiscaller.net

WhoIsCaller : Free caller reviews and voting service

Page Load Speed

1.5 sec in total

First Response

234 ms

Resources Loaded

1.2 sec

Page Rendered

94 ms

whoiscaller.net screenshot

About Website

Click here to check amazing Who Is Caller content for Turkey. Otherwise, check out these important facts you probably never knew about whoiscaller.net

Truecaller is transforming today’s phonebook to make it more intelligent and useful.​

Visit whoiscaller.net

Key Findings

We analyzed Whoiscaller.net page load time and found that the first response time was 234 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

whoiscaller.net performance score

0

Network Requests Diagram

whoiscaller.net

234 ms

css

16 ms

main-stylus-7a80262b33.css

437 ms

modernizr.custom.16777.js

118 ms

main-4fbb8b5439.js

581 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 12% of them (4 requests) were addressed to the original Whoiscaller.net, 35% (12 requests) were made to Truecaller-website-public.s3-eu-west-1.amazonaws.com and 15% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (581 ms) relates to the external source Truecaller-website-public.s3-eu-west-1.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 549.7 kB (70%)

Content Size

788.0 kB

After Optimization

238.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whoiscaller.net main page is 788.0 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. 55% of websites need less resources to load. CSS take 370.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 46.7 kB

  • Original 59.2 kB
  • After minification 56.7 kB
  • After compression 12.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. 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 46.7 kB or 79% of the original size.

Image Optimization

-21%

Potential reduce by 17.1 kB

  • Original 82.7 kB
  • After minification 65.5 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. Obviously, Who Is Caller needs image optimization as it can save up to 17.1 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 175.4 kB

  • Original 275.6 kB
  • After minification 275.3 kB
  • After compression 100.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 175.4 kB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 310.5 kB

  • Original 370.5 kB
  • After minification 369.8 kB
  • After compression 60.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. Whoiscaller.net needs all CSS files to be minified and compressed as it can save up to 310.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (24%)

Requests Now

25

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whoiscaller.net

whoiscaller.net

234 ms

css

css

16 ms

main-stylus-7a80262b33.css

main-stylus-7a80262b33.css

437 ms

modernizr.custom.16777.js

modernizr.custom.16777.js

118 ms

main-4fbb8b5439.js

main-4fbb8b5439.js

581 ms

analytics.js

analytics.js

34 ms

logo.png

logo.png

87 ms

google.png

google.png

177 ms

windows-live.png

windows-live.png

180 ms

blue-search-icon.png

blue-search-icon.png

434 ms

top-spammer-icon.png

top-spammer-icon.png

433 ms

google-play-badge.png

google-play-badge.png

441 ms

app-store-badge.png

app-store-badge.png

526 ms

windows-store-badge.png

windows-store-badge.png

441 ms

truemessenger.png

truemessenger.png

477 ms

collect

collect

41 ms

cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf

cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf

36 ms

DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf

DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf

38 ms

MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf

MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf

37 ms

1sNiewGmvJI

1sNiewGmvJI

141 ms

header-background.png

header-background.png

396 ms

drop-down-arrow.png

drop-down-arrow.png

352 ms

collect

collect

131 ms

country-selector

country-selector

70 ms

www-player-vflMqr8uC.css

www-player-vflMqr8uC.css

12 ms

www-embed-player.js

www-embed-player.js

34 ms

base.js

base.js

71 ms

ga-audiences

ga-audiences

255 ms

id

id

145 ms

YubHWiCUdycrt9r0pwxtCFMvWBBxMHmgtw0lFaZzSbY.js

YubHWiCUdycrt9r0pwxtCFMvWBBxMHmgtw0lFaZzSbY.js

108 ms

ad_status.js

ad_status.js

99 ms

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

49 ms

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

52 ms

watermark_ringo-vflPWbiPS.png

watermark_ringo-vflPWbiPS.png

91 ms

SEO Factors

whoiscaller.net SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whoiscaller.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Whoiscaller.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

whoiscaller.net

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