Tools & Wizards About Us
cresa.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

cresa.com

Home Cresa

Page Load Speed

5.6 sec in total

First Response

48 ms

Resources Loaded

4.4 sec

Page Rendered

1.1 sec

cresa.com screenshot

About Website

Welcome to cresa.com homepage info - get ready to check Cresa best content for United States right away, or after learning these important things about cresa.com

World's largest occupier only commercial real estate company

Visit cresa.com

Key Findings

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

Performance Metrics

cresa.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value16.5 s

0/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value1,010 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.138

79/100

15%

TTI (Time to Interactive)

Value19.1 s

3/100

10%

Network Requests Diagram

cresa.com

48 ms

www.cresa.com

336 ms

swiper.min.js

45 ms

layout

57 ms

main

128 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 87% of them (41 requests) were addressed to the original Cresa.com, 4% (2 requests) were made to Googletagmanager.com and 2% (1 request) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Cresa.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 163.1 kB (3%)

Content Size

4.9 MB

After Optimization

4.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cresa.com main page is 4.9 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. Images take 4.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 74.2 kB

  • Original 90.2 kB
  • After minification 82.9 kB
  • After compression 16.0 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 74.2 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 60.2 kB

  • Original 4.2 MB
  • After minification 4.1 MB

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. Cresa images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 28.2 kB

  • Original 618.5 kB
  • After minification 618.3 kB
  • After compression 590.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. This website has mostly compressed JavaScripts.

CSS Optimization

-76%

Potential reduce by 577 B

  • Original 761 B
  • After minification 354 B
  • After compression 184 B

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. Cresa.com needs all CSS files to be minified and compressed as it can save up to 577 B or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (43%)

Requests Now

42

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cresa.com

cresa.com

48 ms

www.cresa.com

www.cresa.com

336 ms

swiper.min.js

swiper.min.js

45 ms

layout

layout

57 ms

main

main

128 ms

Gilroy.css

Gilroy.css

134 ms

js

js

77 ms

jquery.min.js

jquery.min.js

30 ms

forms.js

forms.js

115 ms

vimeoplayer.js

vimeoplayer.js

204 ms

act-on.js

act-on.js

153 ms

layout

layout

91 ms

libraries-generated.js

libraries-generated.js

3671 ms

polyfill-generated.js

polyfill-generated.js

140 ms

index-generated.js

index-generated.js

424 ms

Language.js

Language.js

161 ms

jquery-2.1.3.min.js

jquery-2.1.3.min.js

315 ms

jquery.validate.min.js

jquery.validate.min.js

288 ms

jquery.validate.unobtrusive.min.js

jquery.validate.unobtrusive.min.js

288 ms

jquery.unobtrusive-ajax.min.js

jquery.unobtrusive-ajax.min.js

287 ms

form.validate.js

form.validate.js

288 ms

form.tracking.js

form.tracking.js

303 ms

gtm.js

gtm.js

124 ms

815364200

815364200

198 ms

Amsterdam_INGHQ_1920x1080.ashx

Amsterdam_INGHQ_1920x1080.ashx

265 ms

play-btn.png

play-btn.png

138 ms

pause-btn.png

pause-btn.png

137 ms

Vibrant-City.ashx

Vibrant-City.ashx

293 ms

Houston-Acq.ashx

Houston-Acq.ashx

294 ms

NY-Battery-Park-Plaza.ashx

NY-Battery-Park-Plaza.ashx

283 ms

Blog-Building-Thumb-2023.ashx

Blog-Building-Thumb-2023.ashx

333 ms

Cresa-Detroit.ashx

Cresa-Detroit.ashx

416 ms

collaboration-award.ashx

collaboration-award.ashx

344 ms

6-6-Placeholder-1.ashx

6-6-Placeholder-1.ashx

441 ms

Careers-background.ashx

Careers-background.ashx

394 ms

Cresa-Logo-inverse.ashx

Cresa-Logo-inverse.ashx

457 ms

fb.svg

fb.svg

371 ms

ig.svg

ig.svg

394 ms

ln.svg

ln.svg

426 ms

tw.svg

tw.svg

427 ms

yt.svg

yt.svg

431 ms

bg.ashx

bg.ashx

412 ms

footer-bg.png

footer-bg.png

387 ms

arrow-dark.png

arrow-dark.png

378 ms

HelveticaNowText.otf

HelveticaNowText.otf

394 ms

HelveticaNowTextBold.otf

HelveticaNowTextBold.otf

407 ms

45331

45331

334 ms

Accessibility Review

cresa.com accessibility score

89

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

cresa.com best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

cresa.com SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

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

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

cresa.com

Open Graph description is not detected on the main page of Cresa. 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: