Tools & Wizards About Us
whitepage.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

whitepage.com

Whitepages - Official Site | Find People, Phone Numbers, Addresses & More

Page Load Speed

23.5 sec in total

First Response

307 ms

Resources Loaded

20.8 sec

Page Rendered

2.4 sec

whitepage.com screenshot

About Website

Click here to check amazing Whitepage content for United States. Otherwise, check out these important facts you probably never knew about whitepage.com

Whitepages - Search, Find, Know | The largest and most trusted online directory with contact information, background checks powered by SmartCheck, and public records for over 90% of US adults.

Visit whitepage.com

Key Findings

We analyzed Whitepage.com page load time and found that the first response time was 307 ms and then it took 23.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

whitepage.com performance score

0

Network Requests Diagram

whitepage.com

307 ms

www.whitepages.com

1180 ms

css

725 ms

application-6c6af233a7cab9da4b0f8087e492d4d5573ea39198e61224d51ec2617925869e.css

1802 ms

gpt.js

1770 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Whitepage.com, 31% (8 requests) were made to Cdnwp.global.ssl.fastly.net and 19% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (7.2 sec) relates to the external source Google-analytics.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.1 MB (68%)

Content Size

3.0 MB

After Optimization

964.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whitepage.com main page is 3.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. 65% of websites need less resources to load. Javascripts take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 74.9 kB

  • Original 99.8 kB
  • After minification 87.2 kB
  • After compression 24.9 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 12.6 kB, which is 13% 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 74.9 kB or 75% of the original size.

Image Optimization

-26%

Potential reduce by 64.0 kB

  • Original 247.5 kB
  • After minification 183.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, Whitepage needs image optimization as it can save up to 64.0 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 1.4 MB

  • Original 2.1 MB
  • After minification 2.1 MB
  • After compression 655.1 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 1.4 MB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 502.0 kB

  • Original 602.8 kB
  • After minification 600.8 kB
  • After compression 100.8 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. Whitepage.com needs all CSS files to be minified and compressed as it can save up to 502.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (53%)

Requests Now

19

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whitepage.com

whitepage.com

307 ms

www.whitepages.com

www.whitepages.com

1180 ms

css

css

725 ms

application-6c6af233a7cab9da4b0f8087e492d4d5573ea39198e61224d51ec2617925869e.css

application-6c6af233a7cab9da4b0f8087e492d4d5573ea39198e61224d51ec2617925869e.css

1802 ms

gpt.js

gpt.js

1770 ms

dstl-wp.js

dstl-wp.js

995 ms

application-460dde6ec2c6c00be2e8be29aa481f4b5c284fd0c44d4002ab7c060491f26a49.js

application-460dde6ec2c6c00be2e8be29aa481f4b5c284fd0c44d4002ab7c060491f26a49.js

3305 ms

index-a3c745d307c50566c906733986f7fcd1e2bab7b8600cad77961a63ba1b30d8e7.js

index-a3c745d307c50566c906733986f7fcd1e2bab7b8600cad77961a63ba1b30d8e7.js

3277 ms

amplitude-3.4.0-min.gz.js

amplitude-3.4.0-min.gz.js

2644 ms

apstag.js

apstag.js

2600 ms

button_googlePlay-5897312ebb54fbe2297753fc4ac128be6f504aecf04a8c67265fde61ca362ed7.png

button_googlePlay-5897312ebb54fbe2297753fc4ac128be6f504aecf04a8c67265fde61ca362ed7.png

2498 ms

button_appStore-266a0f5fec114f198e013bc0b35d87514dfeeaedb79a34cbf73976e71cc52c58.png

button_appStore-266a0f5fec114f198e013bc0b35d87514dfeeaedb79a34cbf73976e71cc52c58.png

2497 ms

pubads_impl_147.js

pubads_impl_147.js

3852 ms

gtm.js

gtm.js

2415 ms

ic-cropped-w-186a2bed5239ed722e7cb0f4f07ebc423bc8fac7e84a7ed22c87515f98bc9bcd.svg

ic-cropped-w-186a2bed5239ed722e7cb0f4f07ebc423bc8fac7e84a7ed22c87515f98bc9bcd.svg

1662 ms

icon_wp_sprite_1x-2b9a55eb22e2e54dd62d09e4a43421d0b9dbd26fba359785077c08334b0b8ac2.png

icon_wp_sprite_1x-2b9a55eb22e2e54dd62d09e4a43421d0b9dbd26fba359785077c08334b0b8ac2.png

1686 ms

print-c64d0125dbc8b699498a5ad634bcb87761578fe00e8314722de98a95dbf64115.css

print-c64d0125dbc8b699498a5ad634bcb87761578fe00e8314722de98a95dbf64115.css

1137 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

1266 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

1266 ms

Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf

Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf

1266 ms

AwBqWF2kjhlybWamaKMPcaCWcynf_cDxXwCLxiixG1c.ttf

AwBqWF2kjhlybWamaKMPcaCWcynf_cDxXwCLxiixG1c.ttf

1267 ms

yVHpdQrmTj9Kax1tmFSx2qCWcynf_cDxXwCLxiixG1c.ttf

yVHpdQrmTj9Kax1tmFSx2qCWcynf_cDxXwCLxiixG1c.ttf

1234 ms

analytics.js

analytics.js

7174 ms

bid

bid

6782 ms

api.amplitude.com

api.amplitude.com

6578 ms

bat.js

bat.js

462 ms

SEO Factors

whitepage.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whitepage.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Whitepage.com main page’s claimed encoding is . 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

whitepage.com

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