3.1 sec in total
194 ms
2.7 sec
161 ms
Click here to check amazing White Pager content. Otherwise, check out these important facts you probably never knew about whitepager.com
This website is for sale! whitepager.com is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, whitepager.com ...
Visit whitepager.comWe analyzed Whitepager.com page load time and found that the first response time was 194 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
whitepager.com performance score
name
value
score
weighting
Value1.8 s
90/100
10%
Value1.8 s
99/100
25%
Value1.8 s
100/100
10%
Value90 ms
99/100
30%
Value0.202
61/100
15%
Value2.9 s
96/100
10%
194 ms
206 ms
30 ms
26 ms
84 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Whitepager.com, 14% (17 requests) were made to Beenverified.com and 8% (9 requests) were made to Bcp.crwdcntrl.net. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Connect.facebook.net.
Page size can be reduced by 472.5 kB (58%)
814.3 kB
341.8 kB
In fact, the total size of Whitepager.com main page is 814.3 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. 45% of websites need less resources to load. Javascripts take 531.2 kB which makes up the majority of the site volume.
Potential reduce by 35.1 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 35.1 kB or 66% of the original size.
Potential reduce by 156 B
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. White Pager images are well optimized though.
Potential reduce by 349.8 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 349.8 kB or 66% of the original size.
Potential reduce by 87.5 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. Whitepager.com needs all CSS files to be minified and compressed as it can save up to 87.5 kB or 82% of the original size.
Number of requests can be reduced by 82 (81%)
101
19
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of White Pager. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and as a result speed up the page load time.
whitepager.com
194 ms
www.whitepagesoftheworld.com
206 ms
aff_c
30 ms
aff_c
26 ms
www.beenverified.com
84 ms
loading
164 ms
bootstrap.min.css
11 ms
main.css
26 ms
modernizr.custom.js
34 ms
jquery.min.js
29 ms
lodash.min.js
32 ms
bootstrap.min.js
30 ms
handlebars.min.js
78 ms
amplify.store.min.js
77 ms
base64.js
73 ms
utility.js
73 ms
teaserparser.js
73 ms
framerida.helpers.js
82 ms
framerida.js
75 ms
downsell.js
75 ms
runner.js
81 ms
hotjar-25826.js
192 ms
j.php
219 ms
dc.js
232 ms
js
216 ms
m.js
261 ms
track.js
270 ms
heap-3560207488.js
266 ms
prum.min.js
228 ms
gtm.js
260 ms
4dda716b20087af465fdef47ea166bf4.png
262 ms
0f9facbc97517d4aca69afe849312e99.png
240 ms
d9d7404c265cce5b9beac34dd17d02d4.png
279 ms
c0acf3fa4d154ec38ba237128629726f.png
287 ms
197b1a158a2888b93ea3b6247c5627bb.png
317 ms
2007ad41b2d47acd9d7d96b8b55c57c5.png
287 ms
modules-043c1e6abe660c48857202e419ff9d8a.js
174 ms
v.gif
54 ms
636a3703d8eac9f30f2daca21ebc6aac.jpg
119 ms
ab5df240fb1f84fd6b00017e1a846c39.svg
84 ms
__utm.gif
95 ms
i.js
234 ms
0758fe0df8474b5be5d9071b4e34d2174140c4ca.1.js
213 ms
conversion_async.js
192 ms
insight.min.js
208 ms
pixel
216 ms
iva.js
197 ms
oct.js
154 ms
nativeads-0-35923774537c34e6283557e2818f6c2ec1c99642.js
211 ms
h
218 ms
in.php
454 ms
adsct
226 ms
adsct
190 ms
e
142 ms
analytics-0-35923774537c34e6283557e2818f6c2ec1c99642.js
41 ms
e
135 ms
e
133 ms
126 ms
fbevents.js
1192 ms
quant.js
125 ms
dpx.js
113 ms
cc.js
114 ms
p
83 ms
365728.html
15 ms
401246.html
11 ms
pixel
130 ms
activity;src=1901398;type=lrmp;cat=dmp02;u2=85266baea60a0d3a93fef0f6c7de93940071d425138c359b4e4fa662f9b3bfe6a6704fcfe29d7ba7
132 ms
activity;src=1901398;type=lrmp;cat=dmp02;u2=628e0dd2a75770e2e1c6ee6ebcf2b3a785fe4c86be2e243212aa8b0bbe903c66a6704fcfe29d7ba7
126 ms
pixel;r=756689983;a=p-zyKdW7Td_sfXE;fpan=1;fpa=P0-1342913631-1458480162780;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458480162779;tzo=-180;ref=;url=https%3A%2F%2Fwww.beenverified.com%2Flp%2Faf95e6%2F1%2Floading%3Fcity%3D%26fn%3D%257Bfn%257D%26ln%3D%257Bln%257D%26state%3D%257Bstate%257D%26subid%3D%26utm_campaign%3D61%26utm_medium%3Daffiliate%26utm_source%3D1969;ogl=
116 ms
dpx
35 ms
aol
41 ms
58 ms
xrefid.xgi
23 ms
xrefid.xgi
21 ms
net.php
14 ms
mapuser
11 ms
362358.gif
10 ms
pixel
24 ms
378348.gif
17 ms
47154.gif
24 ms
generic
11 ms
362248.gif
6 ms
pixel.gif
69 ms
pixel.gif
34 ms
y_match
5 ms
match_redirect
5 ms
xrefid.xgi
5 ms
29931
77 ms
match_redirect
14 ms
rt=ifr
26 ms
tpid=CE29559E22A4EE56C26FB94A0217AB51
46 ms
js
163 ms
5907
102 ms
generic
75 ms
89 ms
tp=ANXS
42 ms
adsct
61 ms
tpid=1c150906-f2da-4c1c-8019-99474876e474
8 ms
p.skimresources.com
27 ms
tpid=165074357721175551
13 ms
tpidqp=tpid
9 ms
q
12 ms
img
76 ms
0.gif
11 ms
tpid=d412037e-ee9e-11e5-8727-7920940439da
5 ms
lr.gif
39 ms
match_redirect
4 ms
sync
27 ms
iframe
60 ms
match_redirect
4 ms
CE29559E22A4EE56C26FB94A0217AB51
79 ms
img
17 ms
img
51 ms
exelate
2 ms
18 ms
24 ms
17 ms
spotx_match
3 ms
fb_match
6 ms
whitepager.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
whitepager.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Issues were logged in the Issues panel in Chrome Devtools
whitepager.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document doesn't use legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whitepager.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 Whitepager.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.
whitepager.com
Open Graph description is not detected on the main page of White Pager. 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: