Tools & Wizards About Us
addsource.com screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

addsource.com

Addsource | Call & Form Tracking | Pay Per Call & Lead Platform

Page Load Speed

2.6 sec in total

First Response

426 ms

Resources Loaded

1.8 sec

Page Rendered

394 ms

addsource.com screenshot

About Website

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.com

Key Findings

We analyzed Addsource.com page load time and found that the first response time was 426 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

addsource.com performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

Network Requests Diagram

addsource.com

426 ms

www.addsource.com

239 ms

gtm.js

81 ms

wp-emoji-release.min.js

48 ms

style.min.css

70 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 85% of them (93 requests) were addressed to the original Addsource.com, 14% (15 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (649 ms) belongs to the original domain Addsource.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 181.4 kB (43%)

Content Size

419.4 kB

After Optimization

238.0 kB

  • HTML
  • Images

In fact, the total size of Addsource.com main page is 419.4 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. 70% of websites need less resources to load. HTML takes 217.7 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 181.1 kB

  • Original 217.7 kB
  • After minification 209.5 kB
  • After compression 36.6 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 181.1 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 247 B

  • Original 201.7 kB
  • After minification 201.4 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.

Requests Breakdown

Number of requests can be reduced by 63 (74%)

Requests Now

85

After Optimization

22

  • Images
  • JavaScript
  • CSS

The browser has sent 85 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 30 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

addsource.com

addsource.com

426 ms

www.addsource.com

www.addsource.com

239 ms

gtm.js

gtm.js

81 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

48 ms

style.min.css

style.min.css

70 ms

classic-themes.min.css

classic-themes.min.css

50 ms

theme.min.css

theme.min.css

59 ms

style.css

style.css

64 ms

style.min.css

style.min.css

67 ms

all.min.css

all.min.css

77 ms

v4-shims.min.css

v4-shims.min.css

90 ms

public.css

public.css

87 ms

jet-menu-general.css

jet-menu-general.css

92 ms

frontend-legacy.min.css

frontend-legacy.min.css

101 ms

frontend.min.css

frontend.min.css

111 ms

general.min.css

general.min.css

103 ms

eael-2547.css

eael-2547.css

120 ms

jet-elements.css

jet-elements.css

123 ms

jet-elements-skin.css

jet-elements-skin.css

117 ms

elementor-icons.min.css

elementor-icons.min.css

133 ms

swiper.min.css

swiper.min.css

136 ms

post-5022.css

post-5022.css

138 ms

frontend.min.css

frontend.min.css

161 ms

global.css

global.css

173 ms

post-2547.css

post-2547.css

151 ms

post-3438.css

post-3438.css

172 ms

post-2943.css

post-2943.css

175 ms

post-3137.css

post-3137.css

176 ms

ecs-style.css

ecs-style.css

181 ms

css

css

40 ms

fontawesome.min.css

fontawesome.min.css

200 ms

solid.min.css

solid.min.css

199 ms

regular.min.css

regular.min.css

196 ms

brands.min.css

brands.min.css

191 ms

jquery.min.js

jquery.min.js

208 ms

jquery-migrate.min.js

jquery-migrate.min.js

217 ms

ecs_ajax_pagination.js

ecs_ajax_pagination.js

234 ms

ecs.js

ecs.js

229 ms

eael-3656.css

eael-3656.css

391 ms

post-3656.css

post-3656.css

224 ms

eael-3648.css

eael-3648.css

358 ms

post-3648.css

post-3648.css

357 ms

animations.min.css

animations.min.css

350 ms

vue.min.js

vue.min.js

344 ms

jet-menu-public-script.js

jet-menu-public-script.js

343 ms

general.min.js

general.min.js

338 ms

eael-2547.js

eael-2547.js

330 ms

imagesloaded.min.js

imagesloaded.min.js

321 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

310 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

309 ms

webpack.runtime.min.js

webpack.runtime.min.js

295 ms

frontend-modules.min.js

frontend-modules.min.js

294 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

295 ms

wp-polyfill.min.js

wp-polyfill.min.js

282 ms

hooks.min.js

hooks.min.js

279 ms

i18n.min.js

i18n.min.js

278 ms

frontend.min.js

frontend.min.js

276 ms

waypoints.min.js

waypoints.min.js

260 ms

core.min.js

core.min.js

244 ms

swiper.min.js

swiper.min.js

241 ms

share-link.min.js

share-link.min.js

239 ms

dialog.min.js

dialog.min.js

241 ms

frontend.min.js

frontend.min.js

239 ms

preloaded-elements-handlers.min.js

preloaded-elements-handlers.min.js

277 ms

jet-elements.min.js

jet-elements.min.js

223 ms

jet-menu-widgets-scripts.js

jet-menu-widgets-scripts.js

260 ms

preloaded-modules.min.js

preloaded-modules.min.js

260 ms

jquery.sticky.min.js

jquery.sticky.min.js

250 ms

AddsourceFinalPurple.png

AddsourceFinalPurple.png

254 ms

CallandFormTracking.png

CallandFormTracking.png

443 ms

PayPerCallSaas.png

PayPerCallSaas.png

254 ms

Marketplace.png

Marketplace.png

263 ms

undraw_content_creator_xeju.svg

undraw_content_creator_xeju.svg

129 ms

undraw_marketing_v0iu.svg

undraw_marketing_v0iu.svg

131 ms

undraw_podcast_q6p7-1.svg

undraw_podcast_q6p7-1.svg

143 ms

capterra_logo.png

capterra_logo.png

229 ms

logo_g2crowd.png

logo_g2crowd.png

409 ms

Hero-BillAble.png

Hero-BillAble.png

310 ms

AddsourceDraw.jpg

AddsourceDraw.jpg

272 ms

Fit-Small-Business-logo2.png

Fit-Small-Business-logo2.png

268 ms

martechtoday-logo_orig.png

martechtoday-logo_orig.png

334 ms

logo_g2crowd-1.png

logo_g2crowd-1.png

428 ms

capterra_logo-1.png

capterra_logo-1.png

386 ms

Gelock2.png

Gelock2.png

434 ms

ha_logo_rgb-2.png

ha_logo_rgb-2.png

448 ms

adzz-logo-1.png

adzz-logo-1.png

492 ms

Layer-2-1.png

Layer-2-1.png

520 ms

AddsourceLogoWhite.png

AddsourceLogoWhite.png

519 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

97 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

129 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

158 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

180 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

179 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

180 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

178 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

177 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

178 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

180 ms

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

181 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

180 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

181 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

182 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

182 ms

fa-solid-900.woff

fa-solid-900.woff

416 ms

fa-solid-900.woff

fa-solid-900.woff

445 ms

fa-regular-400.woff

fa-regular-400.woff

538 ms

fa-regular-400.woff

fa-regular-400.woff

472 ms

eicons.woff

eicons.woff

649 ms

fa-brands-400.woff

fa-brands-400.woff

617 ms

fa-brands-400.woff

fa-brands-400.woff

498 ms

Accessibility Review

addsource.com accessibility score

95

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

Links do not have a discernible name

Best Practices

addsource.com 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

addsource.com SEO score

91

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

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

Social Sharing Optimization

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: