7.1 sec in total
1.3 sec
5.5 sec
271 ms
Click here to check amazing Tishman Speyer content for Brazil. Otherwise, check out these important facts you probably never knew about tishmanspeyer.com.br
Somos responsáveis por empreendimentos como o Rockefeller Center e o Chrysler Center nos Estados Unidos, que são referência mundial, e outros ícones de sustentabilidade ambiental, como o Opern Turm, n...
Visit tishmanspeyer.com.brWe analyzed Tishmanspeyer.com.br page load time and found that the first response time was 1.3 sec and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
tishmanspeyer.com.br performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value20.9 s
0/100
25%
Value18.3 s
0/100
10%
Value12,870 ms
0/100
30%
Value0.049
99/100
15%
Value29.1 s
0/100
10%
1342 ms
92 ms
92 ms
797 ms
620 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 43% of them (37 requests) were addressed to the original Tishmanspeyer.com.br, 9% (8 requests) were made to Fonts.gstatic.com and 7% (6 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Tishmanspeyer.com.br.
Page size can be reduced by 753.1 kB (14%)
5.4 MB
4.6 MB
In fact, the total size of Tishmanspeyer.com.br main page is 5.4 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 4.7 MB which makes up the majority of the site volume.
Potential reduce by 120.5 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 120.5 kB or 81% of the original size.
Potential reduce by 280.2 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. Tishman Speyer images are well optimized though.
Potential reduce by 196.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 196.4 kB or 55% of the original size.
Potential reduce by 156.0 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. Tishmanspeyer.com.br needs all CSS files to be minified and compressed as it can save up to 156.0 kB or 91% of the original size.
Number of requests can be reduced by 30 (41%)
73
43
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tishman Speyer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
tishmanspeyer.com.br
1342 ms
modal-video.min.css
92 ms
font-awesome.css
92 ms
frontend.css
797 ms
origem-2.0.js
620 ms
js
47 ms
frontend.js
862 ms
otSDKStub.js
54 ms
slick.min.css
17 ms
slick-theme.min.css
25 ms
slick.min.js
32 ms
tooltipster.bundle.js
537 ms
jquery.maskedinput.js
279 ms
css
40 ms
tag.js
263 ms
gtm.js
403 ms
ico_phone_number.png
264 ms
jquery.min.js
357 ms
iframe
139 ms
2oqBN71Eo0Sab2Jq_3670d10b21d705113574e7bf943b3823.png
2186 ms
hero_banner_sub.png
321 ms
MGWKBVC4I9loUh0G_8bb65e08eb9128438240a685003ba170.png
879 ms
ico_plus.png
375 ms
Gt0IVp5KNbhPg3bC_7e00c647894ce7b6ef95e96b073122d4.png
2440 ms
ry9HIr2GeLSF4zQu_3cdc0c4263c50734cab2cd88ce572d3c.png
699 ms
REucPvYnHoxSOyNm_1eb12fcf8233280964d5212b23495085.jpg
1480 ms
phpTtOEa6
3359 ms
ZybirO0qNNQWVHty_b0360a79b2165052e06827b0c0cf1ed5.jpg
998 ms
7yyCA7C4gsUKckFM_d149d94ca768c53f4c4331b20cd578da.jpg
1000 ms
ZCXrl2Fs5ec51v83_a9954fb3ca383bd4ca0a1d20debac135.jpg
1222 ms
sUspoKSmyRloE0Rs_552fd096b9e74d1cfef2d49f96a7e271.jpg
1223 ms
6e6d7cad5fffcdb6a3e07ed5b9fa83b60.jpg
1286 ms
bg_ornament_left.png
1288 ms
cache_e759e6d5f7ac9423faf2d411205ab770_400x400_q100_up1_c_b7.jpg
1475 ms
cache_525c7bb18cdba49f1c3943b7009ed69f_400x400_q100_up1_c_b7.jpg
1477 ms
cache_02932dcd92035898830a39dcfd316e17_400x400_q100_up1_c_b7.jpg
1950 ms
cache_a374438da93bb5011dc57427d3479325_400x400_q100_up1_c_b7.jpg
1562 ms
bg_pattern_mid.png
1579 ms
cache_084fc575c9a2a2b4a4fcbe41617f7ead_400x400_q100_up1_c_b7.jpg
1696 ms
cache_d53f820d2a2f9510090ca81ee7bb9698_400x400_q100_up1_c_b7.jpg
1832 ms
cache_c5077b3cb6319233624f913e4e596e97_400x400_q100_up1_c_b7.jpg
2231 ms
cache_aa942f85420177336af28fefd8bf913a_400x400_q100_up1_c_b7.jpg
1972 ms
bg_strip_newsletter.jpg
2083 ms
logo@2x.png
2105 ms
ico_login.png
2317 ms
logo_black.png
2350 ms
nav_arrow_down.png
2373 ms
burger_menu.png
2374 ms
ico_chat.png
2572 ms
ico_email.png
2581 ms
js
266 ms
8839ab81-6882-4df4-8c2c-05ed377f3923-test.json
230 ms
NaPFcZTIAOhVxoMyOr9n_E7fdMbepI5DYZyZ.ttf
214 ms
NaPFcZTIAOhVxoMyOr9n_E7fdMbewI1DYZyZ.ttf
385 ms
NaPFcZTIAOhVxoMyOr9n_E7fdMbe0IhDYZyZ.ttf
387 ms
NaPDcZTIAOhVxoMyOr9n_E7ffGjEGItzZg.ttf
391 ms
NaPDcZTIAOhVxoMyOr9n_E7ffAzHGItzZg.ttf
390 ms
NaPecZTIAOhVxoMyOr9n_E7fdMPmCA.ttf
405 ms
NaPDcZTIAOhVxoMyOr9n_E7ffBzCGItzZg.ttf
390 ms
NaPDcZTIAOhVxoMyOr9n_E7ffHjDGItzZg.ttf
390 ms
fontawesome-webfont.woff
156 ms
update.min.js
186 ms
location
325 ms
analytics.js
248 ms
conversion_async.js
245 ms
fbevents.js
154 ms
pixel.js
724 ms
insight.min.js
374 ms
iframe
87 ms
loader
298 ms
193051821528353
444 ms
iframe
202 ms
otBannerSdk.js
210 ms
246 ms
collect
84 ms
collect
124 ms
collect
126 ms
collect
138 ms
en.json
127 ms
110 ms
ga-audiences
98 ms
otFlat.json
153 ms
otPcCenter.json
221 ms
24 ms
hcrmChatAlert-green.png
459 ms
beacon.php
245 ms
tishmanspeyer.com.br accessibility score
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
tishmanspeyer.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
tishmanspeyer.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
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tishmanspeyer.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Tishmanspeyer.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.
tishmanspeyer.com.br
Open Graph data is detected on the main page of Tishman Speyer. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: