Tools & Wizards About Us
call.app screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

call.app

CallApp - Free Caller ID & Phone Call Blocker app

Page Load Speed

1.3 sec in total

First Response

31 ms

Resources Loaded

945 ms

Page Rendered

347 ms

call.app screenshot

About Website

Click here to check amazing Call content. Otherwise, check out these important facts you probably never knew about call.app

Free Caller ID, Call Blocker, Call Recorder app that allows mobile users to block phone calls, identify calls, blacklist unwanted callers and much more.

Visit call.app

Key Findings

We analyzed Call.app page load time and found that the first response time was 31 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

call.app performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value4.3 s

77/100

10%

TBT (Total Blocking Time)

Value750 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

call.app

31 ms

style.min.css

12 ms

main.app.css

25 ms

classic-themes.min.css

26 ms

css

68 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 86% of them (62 requests) were addressed to the original Call.app, 7% (5 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (168 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 52.4 kB (6%)

Content Size

901.5 kB

After Optimization

849.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Call.app main page is 901.5 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. 75% 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 622.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 50.3 kB

  • Original 62.1 kB
  • After minification 57.2 kB
  • After compression 11.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 50.3 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 1.1 kB

  • Original 622.1 kB
  • After minification 621.0 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. Call images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.0 kB

  • Original 217.2 kB
  • After minification 217.2 kB
  • After compression 216.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.

Requests Breakdown

Number of requests can be reduced by 45 (70%)

Requests Now

64

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

call.app

call.app

31 ms

style.min.css

style.min.css

12 ms

main.app.css

main.app.css

25 ms

classic-themes.min.css

classic-themes.min.css

26 ms

css

css

68 ms

geotarget-public.min.css

geotarget-public.min.css

23 ms

a11y-toolbar.css

a11y-toolbar.css

24 ms

a11y.css

a11y.css

23 ms

a11y-fontsize.css

a11y-fontsize.css

24 ms

wpa-style.css

wpa-style.css

28 ms

wp-show-posts-min.css

wp-show-posts-min.css

27 ms

style.css

style.css

33 ms

elementor-icons.min.css

elementor-icons.min.css

26 ms

frontend-legacy.min.css

frontend-legacy.min.css

25 ms

frontend.min.css

frontend.min.css

27 ms

post-4318.css

post-4318.css

36 ms

all.min.css

all.min.css

39 ms

v4-shims.min.css

v4-shims.min.css

37 ms

global.css

global.css

38 ms

jquery.min.js

jquery.min.js

38 ms

jquery-migrate.min.js

jquery-migrate.min.js

38 ms

v4-shims.min.js

v4-shims.min.js

68 ms

js

js

168 ms

embed.js

embed.js

75 ms

main.app.js

main.app.js

72 ms

geotarget-public.js

geotarget-public.js

68 ms

selectize.min.js

selectize.min.js

70 ms

wpa-toolbar.js

wpa-toolbar.js

68 ms

a11y.js

a11y.js

68 ms

gtm4wp-contact-form-7-tracker.js

gtm4wp-contact-form-7-tracker.js

68 ms

gtm4wp-form-move-tracker.js

gtm4wp-form-move-tracker.js

69 ms

navigation.js

navigation.js

70 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

70 ms

scripts.js

scripts.js

70 ms

api.js

api.js

73 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

70 ms

wp-polyfill.min.js

wp-polyfill.min.js

71 ms

index.js

index.js

71 ms

wp-accessibility.js

wp-accessibility.js

71 ms

longdesc.button.js

longdesc.button.js

71 ms

main.min.js

main.min.js

64 ms

gtm.js

gtm.js

138 ms

header-img.jpg

header-img.jpg

107 ms

logo.png

logo.png

106 ms

logo-home.png

logo-home.png

105 ms

menu-toggle.png

menu-toggle.png

105 ms

search-sq-blue-transp.png

search-sq-blue-transp.png

104 ms

google-play-sprite.png

google-play-sprite.png

104 ms

feature_01_ID-1.png

feature_01_ID-1.png

107 ms

feature_02.png

feature_02.png

107 ms

feature_15_recording_1-e1623738782719.png

feature_15_recording_1-e1623738782719.png

107 ms

tilt_screens_left_VR-e1625487715737.png

tilt_screens_left_VR-e1625487715737.png

127 ms

tilt_screens_Right_double_Message_Id-1-e1625639676616.png

tilt_screens_Right_double_Message_Id-1-e1625639676616.png

127 ms

Home_banner_01.jpg

Home_banner_01.jpg

110 ms

google-play-sprite-2.png

google-play-sprite-2.png

110 ms

feature_13_01_01.png

feature_13_01_01.png

127 ms

press-2.png

press-2.png

107 ms

rsz_31.png

rsz_31.png

127 ms

rsz_androidpolice-logo-with-bg-242x242_1-e1473936923434.png

rsz_androidpolice-logo-with-bg-242x242_1-e1473936923434.png

128 ms

EtxjSSKk_reasonably_small-e1473936781351.jpg

EtxjSSKk_reasonably_small-e1473936781351.jpg

127 ms

site-footer-top-soc-sprite.png

site-footer-top-soc-sprite.png

123 ms

bottom_bar_isometric_mockups-1-e1706109585369.webp

bottom_bar_isometric_mockups-1-e1706109585369.webp

123 ms

site-footer-site-footer-bottom-soc-sprite-hover2.png

site-footer-site-footer-bottom-soc-sprite-hover2.png

123 ms

back-to-top.png

back-to-top.png

123 ms

give_consent.png

give_consent.png

122 ms

recaptcha__en.js

recaptcha__en.js

131 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

35 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

36 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

89 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

95 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

95 ms

a11y.woff

a11y.woff

20 ms

Accessibility Review

call.app accessibility score

80

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

call.app best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

call.app SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Call.app 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 Call.app 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.

Social Sharing Optimization

call.app

Open Graph data is detected on the main page of Call. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: