7.5 sec in total
338 ms
5.4 sec
1.8 sec
Click here to check amazing Global Whoscall content for Japan. Otherwise, check out these important facts you probably never knew about global.whoscall.com
Whoscall helps you identify unknown callers and SMSs. No more spam and telemarketing calls from now on! Need a caller ID finder? Download for free now!
Visit global.whoscall.comWe analyzed Global.whoscall.com page load time and found that the first response time was 338 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
global.whoscall.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value8.2 s
2/100
25%
Value9.3 s
13/100
10%
Value3,030 ms
2/100
30%
Value0.07
96/100
15%
Value22.9 s
1/100
10%
338 ms
667 ms
165 ms
537 ms
34 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Global.whoscall.com, 53% (70 requests) were made to Assets.whoscall.com and 12% (16 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Assets.whoscall.com.
Page size can be reduced by 514.2 kB (19%)
2.7 MB
2.2 MB
In fact, the total size of Global.whoscall.com main page is 2.7 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 195.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. 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 195.9 kB or 69% of the original size.
Potential reduce by 261.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, Global Whoscall needs image optimization as it can save up to 261.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 56.7 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 56.7 kB or 25% of the original size.
Potential reduce by 103 B
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. Global.whoscall.com has all CSS files already compressed.
Number of requests can be reduced by 44 (40%)
109
65
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Global Whoscall. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
global.whoscall.com
338 ms
global.whoscall.com
667 ms
165 ms
en
537 ms
5-70806f4d.chunk.css
34 ms
application-8d55ee22.chunk.css
39 ms
application-d3c020b63e4264b4fd260cc1349aec1118be81aa4a332842d6e314d1ce835988.css
48 ms
js
504 ms
js
882 ms
application-afd30f297917a3f6cca1a357052505bf6977ddd7eff0c8b55fd47ee64fee78a7.js
73 ms
runtime~application-9968b3c41a4782449675.js
72 ms
5-14cfef8526127f3b8e89.chunk.js
89 ms
application-23d1ac204a6bc2f9f958.chunk.js
99 ms
gtm.js
832 ms
gtm.js
833 ms
fbevents.js
832 ms
gtm.js
832 ms
download-qrcode-huawei-260.png
826 ms
hotjar-2648013.js
996 ms
logo-1ac05e55a23c9d1d8319e8ec752b8f98.svg
453 ms
08421437-1aca-4f30-a302-249b77cd3ee0.png
537 ms
hero-deco-left-38f79dc73360dd332b0833129ad5893a.svg
534 ms
hero-deco-right-320d18f9859768da586a4cf2651816c2.svg
531 ms
index-hero-badge-en-120a7dc06c7a67baefde62d403cf1584.svg
531 ms
app-store-badge-f0b2da6ae624c644b0ad82d76dc94191.svg
450 ms
google-play-badge-6719dbfca6574b355c1bdf1bff049459.svg
537 ms
app-gallery-badge-6c9f407509135ca6dca831d2227ded63.svg
536 ms
award-badges-mobile-en-fd9e8580d3a439318d06dc9586642bd8.svg
660 ms
award-badges-en-a8644de1a4ce6b913e25979c36091c4f.svg
656 ms
ic-quote-left-e66f39cb088ac05390f389a5834cfc4e.svg
804 ms
ic-quote-right-b3c33582abf798c038fff02bc7d71b20.svg
802 ms
index-feature-bg-9582f8ecc5573fb822e14aea625917e2.svg
801 ms
w266_b8fb35cc-2f8a-4b81-bead-283ddd09e630.png
803 ms
w266_8ce117b8-ce27-4e1f-a7dd-99bef6a8f405.png
2052 ms
w266_e2bb9a6f-6abb-4832-8bf6-16dbdadfadb3.png
1011 ms
w266_447d87d7-1c40-4bcc-ad61-df2e480badce.png
2053 ms
w266_364d37bf-7dce-4571-bf6c-ef61db56c6dc.png
807 ms
w266_0d9a3277-ca1f-4563-8880-e0c8b3011d18.png
2053 ms
w266_cc397c6d-14dc-4830-9dbf-bf781b0ebaf0.png
2052 ms
w266_9096571b-de5b-4983-a63a-fd07eade9e89.png
1010 ms
index-sticky-feature-bg-416db6d161bd62bc3ea84e626e490dd4.svg
2050 ms
c88d7896-2fae-412e-ae1a-038bc75afef2.svg
1014 ms
w400_91d6baa9-7691-46c9-95e2-2834642974a1.png
1016 ms
2fa0ffbc-51c1-4d50-91a4-ae34846cd284.svg
1017 ms
w400_e1ce1111-308a-420d-aafa-91a7b431c5ed.png
1019 ms
b9a46ee1-0d96-4e8b-9d0b-e44866c9df98.svg
1020 ms
w400_1963ce68-4f7e-4205-87b5-26ce9eedcee6.png
1022 ms
5ec98f11-bfba-42fa-a118-61873ecd69ef.svg
1023 ms
w400_ee32f3a4-54f7-45a8-8551-0510b1585b53.png
1024 ms
a3b1c712-b575-4e21-8af0-6d1dde5e6d91.svg
1025 ms
index-400.jpg
1010 ms
index-1500.jpg
1012 ms
w400_ae5da391-3473-48a4-a176-88ed3e873071.png
1015 ms
3f7ee554-7bb6-4839-b27b-123a9a37ff14.svg
998 ms
w400_422f2ebb-d20d-4707-b52d-5ccb96c9324f.png
989 ms
css
921 ms
webfont.js
732 ms
3048c992-e4b5-441a-af8d-d1f054ed1917.svg
767 ms
polyfillObjectFit-a9fa308df6cec3a381c2.chunk.js
1658 ms
w400_f4a37e98-b337-45b8-8a3d-16dd343fc547.png
1776 ms
js
508 ms
js
496 ms
js
496 ms
64f122a7-17d9-4655-8243-f291574a53b9.svg
1645 ms
w400_d17a1072-183f-4b6a-9f27-60778e4c2224.png
1695 ms
at_1x_9f86d5bb-61a4-4d35-8dd5-006c82dc998a.png
1692 ms
at_1x_311613fb-1ec9-4a82-a169-d0bd28ae607a.jpg
1691 ms
at_1x_6dd41e77-c5a8-488e-a076-fa9432c58563.jpg
1690 ms
at_1x_65bb7635-7353-40dc-aae4-20a58b52114e.jpg
1943 ms
at_1x_e2a8fcb0-b829-472d-9bd9-01cd318f5913.jpg
1886 ms
at_1x_2fe07fea-1010-4f84-9450-78b61578005c.jpg
1826 ms
at_1x_30240ca7-05d0-4f08-be31-0da15f6e1c8c.jpg
1761 ms
world-map-aa88b757f2d5e590cc964c301287ce49.svg
1681 ms
trust-icon-trophy-1eb9f28e7642ea4331efe1b35c61a5d6.svg
1678 ms
trust-icon-database-e794cf4578b74948f7c3241794cebdf4.svg
1869 ms
trust-icon-block-8622c1f536d7002ebeebb6ee374d6864.svg
1870 ms
905374784371184
169 ms
124b5160-8dae-41dd-9236-520fbd275234.png
1790 ms
27844738-5dbf-47ed-a91d-08f6c410ffe2.png
1772 ms
edf3cd4c-5c8d-45e9-87e2-38e9b5ce3d33.png
1665 ms
7812138b-5dff-4b9c-a0ed-74e51c1162d5.png
1655 ms
15340b8b-ca87-4c91-bdf6-f904ea11df9c.png
1844 ms
c2a8c684-a73c-436a-b9d2-8afa662aa0ed.png
1765 ms
fea61378-c4c7-4d8e-baa9-0535ef059c19.png
1839 ms
70a47ce0-6223-4ac6-a400-d961a214c287.png
1837 ms
07a9da66-7f2e-4baa-a923-e5be58901dea.png
1836 ms
eb69aad0-f85c-44ea-a415-48f20931cfc8.png
1834 ms
index-download-bg-5bd89e0a1a23f9a40199d29577cd911b.svg
1831 ms
download-app-icon-74ea8cde13dea4ba553e8b99e7ecfe59.svg
1833 ms
fbe30978-c515-47bd-967f-1b6d2078bff3.gif
1835 ms
js
497 ms
destination
493 ms
events.js
808 ms
908 ms
902 ms
destination
816 ms
insight.min.js
1368 ms
KFOmCnqEu92Fr1Mu4mxM.woff
1361 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
1436 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
1713 ms
font
1714 ms
-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz75KyzC1EsQ.woff
1718 ms
-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz70e1zC1EsQ.woff
1717 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35zS1Q.woff
1717 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj35zS1Q.woff
1716 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk35zS1Q.woff
1715 ms
iJWnBXeUZi_OHPqn4wq6hQ2_hbJ1xyN9wd43SofNWcd1MKVQt_So_9CdU5RtlzZ0Rg.woff
1791 ms
iJWnBXeUZi_OHPqn4wq6hQ2_hbJ1xyN9wd43SofNWcd1MKVQt_So_9CdU6ZtlzZ0Rg.woff
1864 ms
iJWnBXeUZi_OHPqn4wq6hQ2_hbJ1xyN9wd43SofNWcd1MKVQt_So_9CdU3NqlzZ0Rg.woff
1865 ms
k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaG9_FrYtHaw.woff
1792 ms
k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaG-3FrYtHaw.woff
1863 ms
k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaGzjCrYtHaw.woff
1792 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuoySLPg9w.woff
1863 ms
1055 ms
modules.84f80a92c39bbd76564a.js
1132 ms
725 ms
928 ms
1098500811514980
494 ms
613 ms
main.MTNhZGZiOTRkNA.js
386 ms
index-1200.jpg
120 ms
undefined
381 ms
index-3000.jpg
381 ms
398 ms
558 ms
557 ms
en
648 ms
298 ms
303 ms
insight.beta.min.js
286 ms
li_sync
111 ms
global.whoscall.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
global.whoscall.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
global.whoscall.com 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
Tap targets are not sized appropriately
EN
EN
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Global.whoscall.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 Global.whoscall.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.
global.whoscall.com
Open Graph data is detected on the main page of Global Whoscall. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: