2.5 sec in total
543 ms
1.4 sec
558 ms
Welcome to prankcaller.io homepage info - get ready to check Prank Caller best content for United States right away, or after learning these important things about prankcaller.io
Easily Send Prank Calls. Easy to use and works on any phone, tablet or computer. Start sending prank calls to your friends today.
Visit prankcaller.ioWe analyzed Prankcaller.io page load time and found that the first response time was 543 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
prankcaller.io performance score
name
value
score
weighting
Value1.6 s
94/100
10%
Value12.2 s
0/100
25%
Value7.9 s
22/100
10%
Value1,770 ms
10/100
30%
Value0.117
85/100
15%
Value16.4 s
5/100
10%
543 ms
36 ms
474 ms
60 ms
34 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 54% of them (29 requests) were addressed to the original Prankcaller.io, 15% (8 requests) were made to Pranks.prankcaller.io and 13% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (701 ms) belongs to the original domain Prankcaller.io.
Page size can be reduced by 408.5 kB (12%)
3.5 MB
3.0 MB
In fact, the total size of Prankcaller.io main page is 3.5 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. 70% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 387.6 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 387.6 kB or 83% of the original size.
Potential reduce by 19.7 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 Caller images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 22 (52%)
42
20
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prank 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 23 to 1 for JavaScripts and as a result speed up the page load time.
prankcaller.io
543 ms
66592da7d119b763.css
36 ms
polyfills-c67a75d1b6f99dc8.js
474 ms
8624.2fb25f990e4fecea.js
60 ms
webpack-431aff5a5b39124b.js
34 ms
framework-79bce4a3a540b080.js
70 ms
main-385db06d9ee47c53.js
70 ms
_app-5df9b28d5ed7e098.js
173 ms
fc95cc1f-c60c7c0405c2ff7b.js
70 ms
5518-5ee8e6cc9259325d.js
94 ms
2969-b5756cd976c8c7c5.js
94 ms
1216-0961b4ec2559ace1.js
93 ms
1337-bb66668ff1364651.js
96 ms
9395-2620d5968593aeb4.js
170 ms
6185-f8edc0802f35253b.js
103 ms
index-293f34d93d65fb06.js
129 ms
_buildManifest.js
128 ms
_ssgManifest.js
129 ms
client.min.js
67 ms
apple-pay.min.js
79 ms
js
99 ms
webrtc-adapter.js
566 ms
icon
85 ms
style.css
423 ms
2-large.png
149 ms
prankbox-doorstep.png
135 ms
336-large.png
523 ms
349-large.png
162 ms
3-large.png
173 ms
345-large.png
523 ms
362-large.png
523 ms
355-large.png
524 ms
332-large.png
525 ms
menu-icon.png
371 ms
brandpr-logo.webp
520 ms
callIcon.png
520 ms
likeIcon.png
686 ms
customizable-12e179c581ea1ecb28a1808ed48d910e.svg
701 ms
erk7o66rp0
95 ms
42 ms
clarity.js
17 ms
30 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff
22 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff
26 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff
40 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff
35 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff
40 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff
39 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w9.woff
40 ms
ProximaSoft-Medium.woff
328 ms
ProximaSoft-SemiBold.woff
346 ms
ProximaSoft-Light.woff
393 ms
ProximaSoft-Bold.woff
404 ms
c.gif
7 ms
prankcaller.io 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Image elements do not have [alt] attributes
prankcaller.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
prankcaller.io SEO score
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 Prankcaller.io 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 Prankcaller.io 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.
prankcaller.io
Open Graph data is detected on the main page of Prank Caller. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: