5.6 sec in total
1.6 sec
3.7 sec
305 ms
Click here to check amazing Addsource content for Israel. Otherwise, check out these important facts you probably never knew about addsource.com
We made the most powerful tool to enable, monitor, optimize & automate performance based marketing for everyone. Book a live demo today.
Visit addsource.comWe analyzed Addsource.com page load time and found that the first response time was 1.6 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
addsource.com performance score
name
value
score
weighting
Value8.4 s
1/100
10%
Value14.2 s
0/100
25%
Value11.7 s
5/100
10%
Value1,360 ms
17/100
30%
Value0.005
100/100
15%
Value14.0 s
10/100
10%
1571 ms
35 ms
57 ms
83 ms
58 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 74% of them (48 requests) were addressed to the original Addsource.com, 5% (3 requests) were made to Google-analytics.com and 3% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Addsource.com.
Page size can be reduced by 889.9 kB (51%)
1.7 MB
839.5 kB
In fact, the total size of Addsource.com main page is 1.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. 65% of websites need less resources to load. Images take 587.8 kB which makes up the majority of the site volume.
Potential reduce by 34.8 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 4.7 kB, which is 11% 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 34.8 kB or 80% of the original size.
Potential reduce by 19.1 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. Addsource images are well optimized though.
Potential reduce by 377.0 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 377.0 kB or 68% of the original size.
Potential reduce by 459.1 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. Addsource.com needs all CSS files to be minified and compressed as it can save up to 459.1 kB or 85% of the original size.
Number of requests can be reduced by 29 (48%)
60
31
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Addsource. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.addsource.com
1571 ms
wp-emoji-release.min.js
35 ms
dm-style.min.css
57 ms
bootstrap.min.css
83 ms
style.css
58 ms
style.css
61 ms
flickity.min.css
18 ms
css
26 ms
prettyPhoto.css
62 ms
animate.css
63 ms
font-awesome.min.css
88 ms
jquery.js
119 ms
jquery-migrate.min.js
86 ms
jquery.flexslider.min.js
86 ms
jquery.tinycarousel.js
94 ms
headroom.min.js
13 ms
jQuery.headroom.min.js
13 ms
script.js
116 ms
viewportchecker.js
139 ms
jquery.stellar.min.js
142 ms
bootstrap.min.js
144 ms
jquery.prettyPhoto.js
138 ms
jquery.isotope.min.js
157 ms
main.js
155 ms
flickity.pkgd.min.js
6 ms
wp-embed.min.js
152 ms
analytics.js
6 ms
linkid.js
6 ms
collect
297 ms
collect
310 ms
5GOXPVZWjhg
291 ms
logo-white.png
45 ms
logo.png
42 ms
missing-part.jpg
173 ms
buy-virtual-number.png
66 ms
point-your-number.png
154 ms
publish-new-number.png
154 ms
track-calls.png
154 ms
make-money.png
154 ms
calls-report-demo.gif
386 ms
browser-mockup.png
163 ms
buy-numbers-demo.gif
266 ms
calls-status-demo.gif
291 ms
17980ab.jpg
165 ms
the-pro.png
169 ms
2key.png
185 ms
chcago-airduct.png
195 ms
er-rooter.png
195 ms
5star.png
214 ms
goteq.png
222 ms
greatkosher.png
222 ms
smartglass.png
244 ms
bull.png
251 ms
papa.png
250 ms
ms-glass.png
273 ms
1andonly.png
279 ms
logo.png
278 ms
fontawesome-webfont.woff
293 ms
ga-audiences
76 ms
www-embed-player-vflfNyN_r.css
37 ms
www-embed-player.js
65 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
20 ms
ad_status.js
36 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
32 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
34 ms
addsource.com 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.
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
Links do not have a discernible name
addsource.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
addsource.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Addsource.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 Addsource.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.
addsource.com
Open Graph data is detected on the main page of Addsource. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: