Tools & Wizards About Us
idcontact.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 79% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

idcontact.com

Scal-e | Agile marketing platform | Customer Data Platform | Data & loyalty

Page Load Speed

3.5 sec in total

First Response

496 ms

Resources Loaded

2.4 sec

Page Rendered

582 ms

idcontact.com screenshot

About Website

Click here to check amazing Idcontact content for France. Otherwise, check out these important facts you probably never knew about idcontact.com

Customer Data Platform - The B2B & B2C brands' cloud marketing platform for customer acquisition & loyalty

Visit idcontact.com

Key Findings

We analyzed Idcontact.com page load time and found that the first response time was 496 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

idcontact.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value15.8 s

0/100

25%

SI (Speed Index)

Value7.8 s

23/100

10%

TBT (Total Blocking Time)

Value4,410 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.165

71/100

15%

TTI (Time to Interactive)

Value15.0 s

7/100

10%

Network Requests Diagram

scal-e.com

496 ms

css2

45 ms

css2

63 ms

css2

68 ms

gsap.min.js

39 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Idcontact.com, 22% (14 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (814 ms) relates to the external source Scal-e.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 307.9 kB (21%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Idcontact.com main page is 1.5 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. 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. Javascripts take 823.8 kB which makes up the majority of the site volume.

HTML Optimization

-100%

Potential reduce by 123.5 kB

  • Original 123.5 kB
  • After compression 8 B

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. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 123.5 kB or 100% of the original size.

Image Optimization

-8%

Potential reduce by 40.8 kB

  • Original 481.8 kB
  • After minification 441.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. Idcontact images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 126.5 kB

  • Original 823.8 kB
  • After minification 823.8 kB
  • After compression 697.4 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 126.5 kB or 15% of the original size.

CSS Optimization

-25%

Potential reduce by 17.2 kB

  • Original 67.6 kB
  • After minification 67.6 kB
  • After compression 50.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. Idcontact.com needs all CSS files to be minified and compressed as it can save up to 17.2 kB or 25% of the original size.

Requests Breakdown

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

Requests Now

48

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

scal-e.com

scal-e.com

496 ms

css2

css2

45 ms

css2

css2

63 ms

css2

css2

68 ms

gsap.min.js

gsap.min.js

39 ms

styles.css

styles.css

170 ms

styles.css

styles.css

239 ms

cookie-law-info-public.css

cookie-law-info-public.css

257 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

255 ms

app.css

app.css

481 ms

language-cookie.js

language-cookie.js

321 ms

jquery.min.js

jquery.min.js

402 ms

jquery-migrate.min.js

jquery-migrate.min.js

333 ms

cookie-law-info-public.js

cookie-law-info-public.js

340 ms

app.js

app.js

515 ms

js

js

86 ms

adsbygoogle.js

adsbygoogle.js

112 ms

cookie-law-info-table.css

cookie-law-info-table.css

321 ms

index.js

index.js

338 ms

index.js

index.js

346 ms

api.js

api.js

35 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

434 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

434 ms

wp-polyfill.min.js

wp-polyfill.min.js

435 ms

index.js

index.js

532 ms

app.min.js

app.min.js

814 ms

gtm.js

gtm.js

147 ms

01ENG.png

01ENG.png

102 ms

02ENG.png

02ENG.png

171 ms

03ENG.png

03ENG.png

103 ms

04ENG.png

04ENG.png

101 ms

arrow-down-small.svg

arrow-down-small.svg

100 ms

arrow-right-blue.svg

arrow-right-blue.svg

169 ms

time.svg

time.svg

170 ms

logo-scale.svg

logo-scale.svg

247 ms

bg-prefooter.jpg

bg-prefooter.jpg

246 ms

recaptcha__en.js

recaptcha__en.js

508 ms

js

js

419 ms

pxiByp8kv8JHgFVrLGT9V1g.woff

pxiByp8kv8JHgFVrLGT9V1g.woff

414 ms

pxiEyp8kv8JHgFVrFJM.woff

pxiEyp8kv8JHgFVrFJM.woff

630 ms

pxiByp8kv8JHgFVrLDz8V1g.woff

pxiByp8kv8JHgFVrLDz8V1g.woff

684 ms

pxiByp8kv8JHgFVrLFj_V1g.woff

pxiByp8kv8JHgFVrLFj_V1g.woff

684 ms

pxiByp8kv8JHgFVrLEj6V1g.woff

pxiByp8kv8JHgFVrLEj6V1g.woff

684 ms

pxiByp8kv8JHgFVrLCz7V1g.woff

pxiByp8kv8JHgFVrLCz7V1g.woff

727 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVQ.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVQ.woff

727 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

683 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff

774 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

727 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GMS5ntw.woff

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GMS5ntw.woff

728 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GCC5ntw.woff

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GCC5ntw.woff

774 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4G1ilntw.woff

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4G1ilntw.woff

773 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GiClntw.woff

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GiClntw.woff

772 ms

logo-scale.svg

logo-scale.svg

299 ms

bg-home.jpg

bg-home.jpg

282 ms

Home-ENG1.png

Home-ENG1.png

424 ms

Real-CDP.png

Real-CDP.png

273 ms

forrester_ENG-1-e1648045870451.png

forrester_ENG-1-e1648045870451.png

277 ms

gettapp_reviews.png

gettapp_reviews.png

278 ms

Capterra_reviews-2.png

Capterra_reviews-2.png

424 ms

appvizer_cdp.png

appvizer_cdp.png

424 ms

appvizer_fid.png

appvizer_fid.png

423 ms

landing

landing

209 ms

256 ms

landing

landing

93 ms

Accessibility Review

idcontact.com accessibility score

92

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

idcontact.com best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

idcontact.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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

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

idcontact.com

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