Access criteo.es. Anuncia de manera más efectiva

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value4,210 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.055

98/100

15%

TTI (Time to Interactive)

Value22.2 s

1/100

10%

66 ms

gtm.js

327 ms

theme.min.css

57 ms

select2.min.css

25 ms

tablepress-combined.min.css

31 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Criteo.es, 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 (798 ms) relates to the external source Tree-nation.com.

Content Size

1.1 MB

After Optimization

671.2 kB

In fact, the total size of Criteo.es main page is 1.1 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. HTML takes 419.8 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 374.0 kB

Original 419.8 kB
After minification 262.8 kB
After compression 45.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 157.0 kB, which is 37% 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 374.0 kB or 89% of the original size.

Image Optimization

-1%

Potential reduce by 2.7 kB

Original 342.9 kB
After minification 340.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.

JavaScript Optimization

-20%

Potential reduce by 45.3 kB

Original 221.7 kB
After minification 221.7 kB
After compression 176.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 45.3 kB or 20% of the original size.

CSS Optimization

-24%

Potential reduce by 34.2 kB

Original 143.0 kB
After minification 143.0 kB
After compression 108.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. Criteo.es needs all CSS files to be minified and compressed as it can save up to 34.2 kB or 24% of the original size.

Requests Now

After Optimization

The browser has sent 67 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.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

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

High

Image elements do not have [alt] attributes

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

High

Links are not crawlable

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

Language and Encoding

Language Detected

ES
Language Claimed

ES
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Criteo.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Criteo.es 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

criteo.es

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:

Report Summary

Performance

Accessibility

Best Practices

SEO

Anuncia de manera más efectiva | ES - Criteo.com

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

gtm.js

theme.min.css

select2.min.css

tablepress-combined.min.css

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

gtm.js

theme.min.css

select2.min.css

tablepress-combined.min.css

tablepress-responsive.min.css

jquery.min.js

jquery-migrate.min.js

cookies.js

track.js

link-rewrite.js

slick.css

bs4.min.js

iframe.min.js

select2.min.js

theme.min.js

scrolllock.min.js

jquery.matchHeight-min.js

gsap.min.js

SplitText.min.js

ScrollTrigger.min.js

slick.min.js

label-co2-website-white-es.png

criteo-logo-orange.svg

criteo-logo-black.svg

criteo-logo-white.svg

Platform-Featured-Image-v2-1.jpg

Por-que-necesitas-una...-Thumbnail.jpg

Resources-Featured-Image-v1-1.jpg

Careers-Featured-Image-v2-1.jpg

arrow-2023-black.svg

play-button-dark.svg

pG.svg

comcast.svg

shopify.svg

Groupm-logo.svg

deliveroo.svg

Criteo-HP-Hero.png

icon-checked.svg

CMP-01-1.svg

Commerce-Media-Platform-icon.svg

Fafetch-Logo.svg

CMP-02-1.svg

Commerce-growth-icon.svg

Newmans-Logo-1.svg