Tools & Wizards About Us

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

criteo--uat.my.salesforce.com

Something went wrong

Page Load Speed

3.7 sec in total

First Response

504 ms

Resources Loaded

3.1 sec

Page Rendered

105 ms

About Website

Visit criteo--uat.my.salesforce.com now to see the best up-to-date Criteo Uat My Salesforce content for United States and also check out these interesting facts you probably never knew about criteo--uat.my.salesforce.com

Salesforce Customer Secure Login Page. Login to your Salesforce Customer Account.

Visit criteo--uat.my.salesforce.com

Key Findings

We analyzed Criteo--uat.my.salesforce.com page load time and found that the first response time was 504 ms and then it took 3.2 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

criteo--uat.my.salesforce.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value5.7 s

52/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.074

95/100

15%

TTI (Time to Interactive)

Value5.5 s

71/100

10%

Network Requests Diagram

criteo--uat.my.salesforce.com

504 ms

sfdc_210.css

120 ms

SfdcSessionBase208.js

224 ms

LoginHint208.js

333 ms

baselogin4.js

331 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 23% of them (12 requests) were addressed to the original Criteo--uat.my.salesforce.com, 45% (24 requests) were made to C1.sfdcstatic.com and 17% (9 requests) were made to C.salesforce.com. The less responsive or slowest element that took the longest time to load (544 ms) relates to the external source C1.sfdcstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (79%)

Content Size

2.1 MB

After Optimization

433.5 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Criteo--uat.my.salesforce.com 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. 65% of websites need less resources to load. CSS take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 7.2 kB

  • Original 11.0 kB
  • After minification 11.0 kB
  • After compression 3.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. 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 7.2 kB or 66% of the original size.

JavaScript Optimization

-67%

Potential reduce by 543.4 kB

  • Original 812.3 kB
  • After minification 808.5 kB
  • After compression 268.8 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 543.4 kB or 67% of the original size.

CSS Optimization

-87%

Potential reduce by 1.1 MB

  • Original 1.3 MB
  • After minification 1.2 MB
  • After compression 160.9 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--uat.my.salesforce.com needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (73%)

Requests Now

49

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

criteo--uat.my.salesforce.com accessibility score

100

Accessibility Issues

Best Practices

criteo--uat.my.salesforce.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

Page has valid source maps

SEO Factors

criteo--uat.my.salesforce.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Criteo--uat.my.salesforce.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 Criteo--uat.my.salesforce.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

Open Graph description is not detected on the main page of Criteo Uat My Salesforce. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: