105.6 sec in total
296 ms
75.6 sec
29.7 sec
Visit prankdial.com now to see the best up-to-date Prank Dial content for United States and also check out these interesting facts you probably never knew about prankdial.com
We're the #1 prank call site on the web! Send pre-recorded prank calls to your friends from a disguised number, then download and share the recorded reactions on Facebook and Twitter!
Visit prankdial.comWe analyzed Prankdial.com page load time and found that the first response time was 296 ms and then it took 105.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
prankdial.com performance score
name
value
score
weighting
Value2.7 s
61/100
10%
Value17.1 s
0/100
25%
Value13.0 s
2/100
10%
Value2,910 ms
3/100
30%
Value0.858
4/100
15%
Value16.2 s
5/100
10%
296 ms
1089 ms
1520 ms
1427 ms
669 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 38% of them (25 requests) were addressed to the original Prankdial.com, 33% (22 requests) were made to Cdn-pranks.prankdial.com and 6% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (17.5 sec) relates to the external source Facebook.com.
Page size can be reduced by 1.3 MB (42%)
3.1 MB
1.8 MB
In fact, the total size of Prankdial.com main page is 3.1 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. 55% of websites need less resources to load. Javascripts take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 145.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 145.0 kB or 87% of the original size.
Potential reduce by 90.3 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. Prank Dial images are well optimized though.
Potential reduce by 976.6 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 976.6 kB or 57% of the original size.
Potential reduce by 89.6 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. Prankdial.com needs all CSS files to be minified and compressed as it can save up to 89.6 kB or 80% of the original size.
Number of requests can be reduced by 28 (48%)
58
30
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prank Dial. 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.
prankdial.com
296 ms
prankdial.com
1089 ms
www.prankdial.com
1520 ms
fbevents.js
1427 ms
newrelic.js
669 ms
vendor.js
0 ms
app.js
0 ms
adsbygoogle.js
1662 ms
extrabold.woff
1462 ms
semibold.woff
1498 ms
1208993655824238
0 ms
analytics.js
2650 ms
prank.js
1447 ms
pd_logo.svg
1247 ms
hamburger.svg
1248 ms
logo_android.svg
1163 ms
logo_apple.svg
16649 ms
cry-rascal.svg
16898 ms
facebook.svg
16901 ms
twitter.svg
16900 ms
null
17272 ms
17479 ms
ec.js
15865 ms
16419 ms
close.svg
987 ms
search.svg
988 ms
system
1296 ms
en-US.png
678 ms
collect
163 ms
pranks
1199 ms
collect
42 ms
nr-963.min.js
8004 ms
down.svg
6592 ms
you-hit-my-car-prank-full-medium.png
11498 ms
you-hit-my-car-prank-full-tiny.png
7036 ms
why-you-call-my-girlfriend-prank-full-medium.png
7037 ms
why-you-call-my-girlfriend-prank-full-tiny.png
6856 ms
why-you-call-my-boyfriend-prank-full-medium.png
7036 ms
why-you-call-my-boyfriend-prank-full-tiny.png
6720 ms
crazy-ol-lady-prank-full-medium.png
6873 ms
crazy-ol-lady-prank-full-tiny.png
6872 ms
you-kick-my-dog-prank-full-medium.png
6955 ms
you-kick-my-dog-prank-full-tiny.png
6873 ms
secret-crush-prank-full-medium.png
6901 ms
secret-crush-prank-full-tiny.png
6897 ms
pizza-delivery-prank-full-medium.png
7037 ms
pizza-delivery-prank-full-tiny.png
6898 ms
why-you-call-me-prank-full-medium.png
6956 ms
why-you-call-me-prank-full-tiny.png
6871 ms
credit-fraud-prank-full-medium.png
7008 ms
credit-fraud-prank-full-tiny.png
6925 ms
wheres-my-paper-prank-full-medium.png
7127 ms
wheres-my-paper-prank-full-tiny.png
6925 ms
chinese-buffet-prank-full-medium.png
7127 ms
checkmark.svg
821 ms
play_big.svg
593 ms
thumb_up.svg
822 ms
sent.svg
479 ms
comments.svg
478 ms
ca-pub-9849719119202726.js
1115 ms
zrt_lookup.html
5344 ms
show_ads_impl.js
2917 ms
chinese-buffet-prank-full-tiny.png
4791 ms
b8d94d40e2
3724 ms
ads
2565 ms
osd.js
1340 ms
prankdial.com accessibility score
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
[aria-*] attributes do not match their roles
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
prankdial.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
prankdial.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prankdial.com 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 Prankdial.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.
prankdial.com
Open Graph data is detected on the main page of Prank Dial. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: