Tools & Wizards About Us
tribeca-stl.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

tribeca-stl.com

Tribeca STL| St. Louis, MO Luxury Apartments in Central West End

Page Load Speed

2.9 sec in total

First Response

18 ms

Resources Loaded

1.4 sec

Page Rendered

1.5 sec

tribeca-stl.com screenshot

About Website

Click here to check amazing Tribeca STL content for United States. Otherwise, check out these important facts you probably never knew about tribeca-stl.com

Tribeca STL offers Studio, 1, 2 & 3 bedroom apartmentson Pershing Ave in St. Louis, MO! Fantastic amenities + Great location near Downtown & Forest Park.

Visit tribeca-stl.com

Key Findings

We analyzed Tribeca-stl.com page load time and found that the first response time was 18 ms and then it took 2.9 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

tribeca-stl.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value3,240 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.364

29/100

15%

TTI (Time to Interactive)

Value19.5 s

2/100

10%

Network Requests Diagram

tribeca-stl.com

18 ms

55 ms

OtAutoBlock.js

43 ms

otSDKStub.js

66 ms

honeybadger.min.js

111 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Tribeca-stl.com, 42% (16 requests) were made to G5-assets-cld-res.cloudinary.com and 16% (6 requests) were made to Res.cloudinary.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source G5-assets-cld-res.cloudinary.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 156.2 kB (7%)

Content Size

2.1 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tribeca-stl.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. 45% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 156.1 kB

  • Original 184.4 kB
  • After minification 168.4 kB
  • After compression 28.3 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 156.1 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 15 B

  • Original 1.7 MB
  • After minification 1.7 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. Tribeca STL images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 79 B

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

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 75.0 kB
  • After minification 75.0 kB
  • After compression 75.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. Tribeca-stl.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 8 (22%)

Requests Now

36

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tribeca-stl.com

tribeca-stl.com

18 ms

55 ms

OtAutoBlock.js

OtAutoBlock.js

43 ms

otSDKStub.js

otSDKStub.js

66 ms

honeybadger.min.js

honeybadger.min.js

111 ms

application-a02ba5c3220f2125f6edd0b47799b0c347b0bcc9.min.css

application-a02ba5c3220f2125f6edd0b47799b0c347b0bcc9.min.css

56 ms

1

1

132 ms

web-theme.min.js

web-theme.min.js

56 ms

date-time.min.js

date-time.min.js

43 ms

form-enhancer.min.js

form-enhancer.min.js

45 ms

application-7be414943f.min.js

application-7be414943f.min.js

36 ms

home-2a84a3597d.min.js

home-2a84a3597d.min.js

43 ms

ec5ace8c-cb28-45ba-97a4-6184b479051c.json

ec5ace8c-cb28-45ba-97a4-6184b479051c.json

43 ms

Tribeca_Logo_mxrm25.png

Tribeca_Logo_mxrm25.png

262 ms

Move-In_Special_tjkwtv.png

Move-In_Special_tjkwtv.png

344 ms

T-Symbol_y9zu6d.png

T-Symbol_y9zu6d.png

273 ms

Floorplans-Front-3_bgtt0y.png

Floorplans-Front-3_bgtt0y.png

473 ms

Amenities-Front_re7z2m.png

Amenities-Front_re7z2m.png

457 ms

Neighborhood-Front_knq9p9.png

Neighborhood-Front_knq9p9.png

383 ms

Tribeca_Logo_mxrm25.png

Tribeca_Logo_mxrm25.png

379 ms

Move-In_Special_tjkwtv.png

Move-In_Special_tjkwtv.png

368 ms

5510-PERSHING-AVE_TRIBECA-APARTMENTS_RPI_II-1736226-35_lf5fgw.jpg

5510-PERSHING-AVE_TRIBECA-APARTMENTS_RPI_II-1736226-35_lf5fgw.jpg

623 ms

Floorplans-Back_ushkya.png

Floorplans-Back_ushkya.png

615 ms

Amenities-Back_frbeva.png

Amenities-Back_frbeva.png

427 ms

Neighborhood-Back_rxtlm5.png

Neighborhood-Back_rxtlm5.png

426 ms

5510-PERSHING-AVE_TRIBECA-APARTMENTS_RPI_II-1736226-20_ryfmry.jpg

5510-PERSHING-AVE_TRIBECA-APARTMENTS_RPI_II-1736226-20_ryfmry.jpg

740 ms

5510-PERSHING-AVE_TRIBECA-APARTMENTS_RPI_II-1736226-22_hm9jkf.jpg

5510-PERSHING-AVE_TRIBECA-APARTMENTS_RPI_II-1736226-22_hm9jkf.jpg

464 ms

5510-PERSHING-AVE_TRIBECA-APARTMENTS_RPI_II-1736226-14_gjh3hd.jpg

5510-PERSHING-AVE_TRIBECA-APARTMENTS_RPI_II-1736226-14_gjh3hd.jpg

554 ms

5510-PERSHING-AVE_TRIBECA-APARTMENTS_RPI_II-1736226-7_v76jfi.jpg

5510-PERSHING-AVE_TRIBECA-APARTMENTS_RPI_II-1736226-7_v76jfi.jpg

514 ms

5510-PERSHING-AVE_TRIBECA-APARTMENTS_RPI_II-1736226-75_revised_unsw07.jpg

5510-PERSHING-AVE_TRIBECA-APARTMENTS_RPI_II-1736226-75_revised_unsw07.jpg

651 ms

5510-PERSHING-AVE_TRIBECA-APARTMENTS_RPI_II-1736226-64_pacgy2.jpg

5510-PERSHING-AVE_TRIBECA-APARTMENTS_RPI_II-1736226-64_pacgy2.jpg

813 ms

5510-PERSHING-AVE_TRIBECA-APARTMENTS_RPI_II-1736226-65_mvxwch.jpg

5510-PERSHING-AVE_TRIBECA-APARTMENTS_RPI_II-1736226-65_mvxwch.jpg

816 ms

5510-PERSHING-AVE_TRIBECA-APARTMENTS_RPI_II-1736226-40_revised_xrxmkz.jpg

5510-PERSHING-AVE_TRIBECA-APARTMENTS_RPI_II-1736226-40_revised_xrxmkz.jpg

1009 ms

wcag2.1AA-blue-v_rhbk9n.png

wcag2.1AA-blue-v_rhbk9n.png

1195 ms

MRR_Logo_REV_xaufi5.png

MRR_Logo_REV_xaufi5.png

866 ms

location

location

338 ms

www.missionrockresidential.com

www.missionrockresidential.com

9 ms

segment

segment

82 ms

Accessibility Review

tribeca-stl.com accessibility score

87

Accessibility Issues

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

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

Best Practices

tribeca-stl.com best practices score

67

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

tribeca-stl.com SEO score

84

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

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

High

Tap targets are not sized appropriately

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 Tribeca-stl.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 Tribeca-stl.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

tribeca-stl.com

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