Tools & Wizards About Us
calltracking.at screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

calltracking.at

CallTracking.at - Marketing Rufnummern & Telefon Tracking

Page Load Speed

5.9 sec in total

First Response

1.3 sec

Resources Loaded

4.4 sec

Page Rendered

129 ms

calltracking.at screenshot

About Website

Click here to check amazing Call Tracking content for Austria. Otherwise, check out these important facts you probably never knew about calltracking.at

Mit Hilfe von Marketingrufnummern (☎) und unserer CallTracking-Lösung (★) messen Sie alle Anrufe punktgenau - egal ob ✔ TV, ✔ Radio, ✔ Online ✔ Print,...

Visit calltracking.at

Key Findings

We analyzed Calltracking.at page load time and found that the first response time was 1.3 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

calltracking.at performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

36/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value5,670 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

www.calltracking.at

1308 ms

css

31 ms

settings.css

127 ms

captions.php

1352 ms

static-captions.css

256 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 89% of them (42 requests) were addressed to the original Calltracking.at, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Calltracking.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 622.3 kB (71%)

Content Size

877.9 kB

After Optimization

255.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Calltracking.at main page is 877.9 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. 50% of websites need less resources to load. Javascripts take 435.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 30.4 kB

  • Original 39.3 kB
  • After minification 37.7 kB
  • After compression 8.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 30.4 kB or 77% of the original size.

Image Optimization

-9%

Potential reduce by 5.6 kB

  • Original 61.8 kB
  • After minification 56.2 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 Tracking images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 296.2 kB

  • Original 435.3 kB
  • After minification 433.9 kB
  • After compression 139.1 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 296.2 kB or 68% of the original size.

CSS Optimization

-85%

Potential reduce by 290.1 kB

  • Original 341.5 kB
  • After minification 269.6 kB
  • After compression 51.4 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. Calltracking.at needs all CSS files to be minified and compressed as it can save up to 290.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (61%)

Requests Now

44

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.calltracking.at

www.calltracking.at

1308 ms

css

css

31 ms

settings.css

settings.css

127 ms

captions.php

captions.php

1352 ms

static-captions.css

static-captions.css

256 ms

checkbox.min.css

checkbox.min.css

255 ms

grid.css

grid.css

256 ms

base.css

base.css

258 ms

layout.css

layout.css

392 ms

shortcodes.css

shortcodes.css

514 ms

magnific-popup.css

magnific-popup.css

385 ms

mediaelementplayer.css

mediaelementplayer.css

388 ms

enfold.css

enfold.css

1632 ms

custom.css

custom.css

509 ms

form.min.css

form.min.css

529 ms

jquery.js

jquery.js

638 ms

jquery-migrate.min.js

jquery-migrate.min.js

628 ms

jquery.themepunch.plugins.min.js

jquery.themepunch.plugins.min.js

758 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

761 ms

gtm4wp-form-move-tracker.js

gtm4wp-form-move-tracker.js

745 ms

avia-compat.js

avia-compat.js

757 ms

avia.js

avia.js

984 ms

shortcodes.js

shortcodes.js

1009 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

881 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

1003 ms

wp-mediaelement.js

wp-mediaelement.js

1000 ms

comment-reply.min.js

comment-reply.min.js

1105 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

1085 ms

6_calltracking.png

6_calltracking.png

129 ms

oliver.jpg

oliver.jpg

131 ms

phil.jpg

phil.jpg

129 ms

googleadwords.64x64.png

googleadwords.64x64.png

128 ms

msdynamics.64x64.png

msdynamics.64x64.png

130 ms

magento.64x64.png

magento.64x64.png

129 ms

sugarcrm.64x64.png

sugarcrm.64x64.png

247 ms

zohocrm.64x64.png

zohocrm.64x64.png

247 ms

jira.64x64.png

jira.64x64.png

251 ms

zendesk.64x64.png

zendesk.64x64.png

249 ms

salesforce.64x64.png

salesforce.64x64.png

251 ms

visa.png

visa.png

252 ms

mastercard.png

mastercard.png

370 ms

entypo-fontello.woff

entypo-fontello.woff

452 ms

gtm.js

gtm.js

60 ms

analytics.js

analytics.js

6 ms

collect

collect

3 ms

collect

collect

76 ms

print.css

print.css

130 ms

Accessibility Review

calltracking.at accessibility score

89

Accessibility Issues

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.

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

Image elements do not have [alt] attributes

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

calltracking.at best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

calltracking.at SEO score

93

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

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Calltracking.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Calltracking.at 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

calltracking.at

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