2.1 sec in total
38 ms
1.1 sec
901 ms
Welcome to criteo.fr homepage info - get ready to check Criteo best content right away, or after learning these important things about criteo.fr
Activate the world’s largest set of commerce data to bring richer experiences to consumers with our Commerce Media Platform
Visit criteo.frWe analyzed Criteo.fr page load time and found that the first response time was 38 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
criteo.fr performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value13.9 s
0/100
25%
Value7.9 s
23/100
10%
Value2,200 ms
6/100
30%
Value0.032
100/100
15%
Value19.8 s
2/100
10%
38 ms
157 ms
41 ms
25 ms
25 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Criteo.fr, 3% (2 requests) were made to Tree-nation.com and 3% (2 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (567 ms) relates to the external source Tree-nation.com.
Page size can be reduced by 465.9 kB (40%)
1.2 MB
688.3 kB
In fact, the total size of Criteo.fr main page is 1.2 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. Only a small number of websites need less resources to load. HTML takes 430.1 kB which makes up the majority of the site volume.
Potential reduce by 383.4 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 161.5 kB, which is 38% 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 383.4 kB or 89% of the original size.
Potential reduce by 3.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. Criteo images are well optimized though.
Potential reduce by 45.3 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 45.3 kB or 20% of the original size.
Potential reduce by 34.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. Criteo.fr needs all CSS files to be minified and compressed as it can save up to 34.1 kB or 24% of the original size.
Number of requests can be reduced by 30 (43%)
70
40
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Criteo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
38 ms
gtm.js
157 ms
theme.min.css
41 ms
select2.min.css
25 ms
tablepress-combined.min.css
25 ms
tablepress-responsive.min.css
25 ms
jquery.min.js
26 ms
jquery-migrate.min.js
34 ms
cookies.js
37 ms
track.js
567 ms
link-rewrite.js
32 ms
slick.css
141 ms
bs4.min.js
141 ms
iframe.min.js
142 ms
select2.min.js
144 ms
theme.min.js
147 ms
scrolllock.min.js
142 ms
jquery.matchHeight-min.js
145 ms
gsap.min.js
146 ms
SplitText.min.js
143 ms
ScrollTrigger.min.js
144 ms
slick.min.js
142 ms
label-co2-website-white-fr.png
430 ms
arrow-2023-black.svg
20 ms
criteo-logo-orange.svg
17 ms
criteo-logo-black.svg
21 ms
criteo-logo-white.svg
19 ms
Header-Nav-Image-380x175-FR.png
19 ms
21-Addressability-Hub-FR-380x175px.png
16 ms
adidas-main-nav.jpg
22 ms
Careers-Featured-Image-v2-1.jpg
21 ms
play-button-dark.svg
24 ms
pG.svg
23 ms
comcast.svg
25 ms
shopify.svg
26 ms
Groupm-logo.svg
29 ms
deliveroo.svg
72 ms
Criteo-HP-Hero.png
34 ms
icon-checked.svg
28 ms
CMP-01-1.svg
35 ms
Commerce-Media-Platform-icon.svg
29 ms
Fafetch-Logo.svg
33 ms
CMP-02-1.svg
114 ms
Commerce-growth-icon.svg
67 ms
Neemans-Logo-1.svg
69 ms
CMP-03-1.svg
72 ms
Commerce-Max-icon.svg
67 ms
Metro_Logo_Black.svg
313 ms
CMP-Image-04-CGrid.svg
320 ms
Commerce-Grid-icon.svg
71 ms
Raptive-Logo.svg
227 ms
Icon-customer-acquisition.svg
229 ms
arrow-2023-white.svg
227 ms
Icon-customer-retention.svg
310 ms
Start-or-scale-retail-media-icon.svg
310 ms
Icon-audiences.svg
369 ms
Icon-dynamic-retargeting.svg
310 ms
Inspire-with-video-icon.svg
373 ms
contextual-ads-icon.svg
309 ms
Protect-your-brand-icon.svg
304 ms
Addressability-Icon-v1.svg
388 ms
carousel-nav-white.svg
303 ms
Aventon-logo.svg
356 ms
arrow-2023-purple.svg
359 ms
Untitled-6.png
386 ms
michaels.svg
358 ms
oneill.svg
358 ms
ContactSales.svg
360 ms
ContactSales-mobile.svg
383 ms
close_btn_black.svg
377 ms
criteo-logo-orange.svg
380 ms
Graphik-Medium-Cy-Web.woff
180 ms
Graphik-Regular-Cy-Web.woff
198 ms
Graphik-Semibold-Cy-Web.woff
205 ms
Mona-Sans-RegularWide.woff
206 ms
fa-brands-400.woff
206 ms
criteo.fr 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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
criteo.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
criteo.fr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Criteo.fr can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed French language. Our system also found out that Criteo.fr 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.
criteo.fr
Open Graph data is detected on the main page of Criteo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: