4.3 sec in total
363 ms
2.4 sec
1.5 sec
Click here to check amazing Criteo content. Otherwise, check out these important facts you probably never knew about criteo.com.br
Ative a maior base de commerce data do mundo para criar experiências enriquecedoras para os consumidores com nossa commerce Media Platform.
Visit criteo.com.brWe analyzed Criteo.com.br page load time and found that the first response time was 363 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
criteo.com.br performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value28.2 s
0/100
25%
Value21.5 s
0/100
10%
Value35,520 ms
0/100
30%
Value0.052
99/100
15%
Value49.3 s
0/100
10%
363 ms
336 ms
107 ms
224 ms
173 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Criteo.com.br, 89% (70 requests) were made to Criteo.com and 3% (2 requests) were made to Tree-nation.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Criteo.com.
Page size can be reduced by 447.2 kB (21%)
2.1 MB
1.7 MB
In fact, the total size of Criteo.com.br main page is 2.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. 80% 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. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 198.7 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 32.3 kB, which is 14% 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 198.7 kB or 84% of the original size.
Potential reduce by 208.7 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. Obviously, Criteo needs image optimization as it can save up to 208.7 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 7.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 7.0 kB or 13% of the original size.
Potential reduce by 32.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.com.br needs all CSS files to be minified and compressed as it can save up to 32.8 kB or 25% of the original size.
Number of requests can be reduced by 14 (21%)
68
54
The browser has sent 68 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 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
criteo.com.br
363 ms
336 ms
gtm.js
107 ms
theme.min.css
224 ms
tablepress-combined.min.css
173 ms
tablepress-responsive.min.css
177 ms
jquery.min.js
180 ms
jquery-migrate.min.js
176 ms
cookies.js
170 ms
track.js
615 ms
link-rewrite.js
161 ms
slick.css
151 ms
bs4.min.js
182 ms
iframe.min.js
182 ms
theme.min.js
321 ms
scrolllock.min.js
320 ms
jquery.matchHeight-min.js
149 ms
slick.min.js
150 ms
criteo-logo-orange.svg
79 ms
globe.svg
83 ms
HP-Hero-Image.svg
798 ms
HP-goals.svg
97 ms
Bemol-ss-logo-min.png
194 ms
ss-logo-Loft.png
80 ms
ss-logo-Pau-a-Pique.png
95 ms
ss-logo-VIVARA.png
187 ms
ss-logo-iplace.png
189 ms
ss-logo-Linio-transparent.png
191 ms
ss-logo-Le-Creuset-min-e1571759437538.png
190 ms
ss-logo-LATAM-Airlines-min.png
192 ms
ss-logo-Metropoles.png
194 ms
SS-logo-santeplus.png
196 ms
SS-logo-coupe-du-monde.png
195 ms
Vibram-Logo_20x20_300dpi-Print-min-1.png
683 ms
58482958cef1014c0b5e49fa-min.png
262 ms
ss-logo-philips-min.png
264 ms
Electrolux_logo_new.png
263 ms
Consumer-Trends-Cover-01.jpg
264 ms
Consumer-Trends-Cover-02.jpg
266 ms
Consumer-Trends-Cover-03.jpg
290 ms
Consumer-Trends-Cover-05.jpg
274 ms
phone-widget.svg
269 ms
criteo-logo-white-footer.svg
319 ms
label-co2-website-white-en.png
579 ms
search.svg
651 ms
CriteoHP-2022.svg
653 ms
Ultimate-Guide-to-CM-BR.svg
813 ms
Billion-Users-Icon.svg
655 ms
Publisher-Icon.svg
662 ms
Interactions-Icon.svg
660 ms
Countries-Icon.svg
658 ms
HurmeGeometricSans4-SemiBold.woff
1029 ms
ApercuPro-Bold.woff
713 ms
HurmeGeometricSans1-Regular.woff
761 ms
ApercuPro.woff
714 ms
HurmeGeometricSans1-SemiBold.woff
1034 ms
fa-solid-900.woff
1031 ms
Awareness-Icon.svg
1002 ms
Consideration-Icon.svg
1004 ms
Conversion-Icon.svg
923 ms
the-stories-bg-1024x480-1.png
929 ms
Bemol-ss-hero.jpg
929 ms
ss-hero-Loft.png
1122 ms
ss-hero-Pau-a-Pique.png
923 ms
ss-hero-Vivara.jpg
1119 ms
arrow-prev-slick.svg
925 ms
arrow-next-slick.svg
927 ms
icon-volume.png
944 ms
list-checkmark.svg
916 ms
Shopper-Graph-Icon.svg
1077 ms
Drive-Value-Icon.png
877 ms
Product-Recommendations-Icon-03.svg
1051 ms
Dynamic-Retargeting-04.svg
1047 ms
Predictive-Bidding-Icon-01.svg
1054 ms
consumer-trends-bg-1024x480-1.png
1042 ms
expand-arrows.svg
1043 ms
fa-brands-400.woff
1017 ms
Prod
761 ms
otSDKStub.js
524 ms
criteo.com.br accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.com.br 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
Page has valid source maps
criteo.com.br 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
Image elements do not have [alt] attributes
Document doesn't have a valid hreflang
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Criteo.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Criteo.com.br 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.com.br
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: