Access auto.callsource.com. Own-Set-Close: Auto Call Tracking, Coaching & Digital Attribution

name

value

score

weighting

FCP (First Contentful Paint)

Value14.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value28.5 s

0/100

10%

TBT (Total Blocking Time)

Value34,740 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.153

75/100

15%

TTI (Time to Interactive)

Value58.1 s

0/100

10%

auto.callsource.com

615 ms

ga.js

28 ms

styles.css

778 ms

flexslider.css

133 ms

jquery-1.8.2.min.js

520 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 67% of them (36 requests) were addressed to the original Auto.callsource.com, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Sugar.callsource.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Auto.callsource.com.

Content Size

2.3 MB

After Optimization

1.4 MB

In fact, the total size of Auto.callsource.com main page is 2.3 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. 40% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 26.6 kB

Original 32.9 kB
After minification 21.6 kB
After compression 6.3 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. This page needs HTML code to be minified as it can gain 11.3 kB, which is 34% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 26.6 kB or 81% of the original size.

Image Optimization

-12%

Potential reduce by 167.6 kB

Original 1.4 MB
After minification 1.2 MB

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, Auto Call Source needs image optimization as it can save up to 167.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 489.3 kB

Original 666.8 kB
After minification 593.8 kB
After compression 177.5 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 489.3 kB or 73% of the original size.

CSS Optimization

-87%

Potential reduce by 187.7 kB

Original 216.4 kB
After minification 176.5 kB
After compression 28.8 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. Auto.callsource.com needs all CSS files to be minified and compressed as it can save up to 187.7 kB or 87% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

[aria-hidden="true"] elements contain focusable descendents

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.

High

Buttons do not have an accessible name

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links do not have descriptive text

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Auto.callsource.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Auto.callsource.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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Auto Call Source. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks:

Report Summary

Performance

Accessibility

Best Practices

SEO

Own-Set-Close: Auto Call Tracking, Coaching & Digital Attribution

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

auto.callsource.com

ga.js

styles.css

flexslider.css

jquery-1.8.2.min.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

{{url}}

Accessibility Review

Accessibility Issues

Best Practices

Areas of Improvement

SEO Factors

Search Engine Optimization Advices

Language and Encoding

Language Detected

Language Claimed

Encoding

Social Sharing Optimization

{{og_title}}