Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

tenement.org

Immigration Museum NYC | Tenement Museum

Page Load Speed

1.1 sec in total

First Response

18 ms

Resources Loaded

888 ms

Page Rendered

219 ms

tenement.org screenshot

About Website

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

The Tenement Museum shares stories of the immigrant and migrant experience through guided tours of two historic tenement buildings in NYC.

Visit tenement.org

Key Findings

We analyzed Tenement.org page load time and found that the first response time was 18 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

tenement.org performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value14.3 s

1/100

10%

TBT (Total Blocking Time)

Value6,300 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value21.8 s

1/100

10%

Network Requests Diagram

tenement.org

18 ms

tenement.org

377 ms

css

59 ms

main.css

25 ms

main.css

26 ms

Our browser made a total of 129 requests to load all elements on the main page. We found that 89% of them (115 requests) were addressed to the original Tenement.org, 3% (4 requests) were made to Support.tenement.org and 2% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (377 ms) belongs to the original domain Tenement.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 364.8 kB (13%)

Content Size

2.9 MB

After Optimization

2.5 MB

In fact, the total size of Tenement.org main page is 2.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. 55% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 38.3 kB

  • Original 47.9 kB
  • After minification 36.2 kB
  • After compression 9.6 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 11.7 kB, which is 24% 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 38.3 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 119.0 kB

  • Original 2.6 MB
  • After minification 2.5 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. Tenement images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 110.5 kB

  • Original 167.5 kB
  • After minification 145.1 kB
  • After compression 57.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 110.5 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 97.0 kB

  • Original 115.2 kB
  • After minification 96.7 kB
  • After compression 18.2 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. Tenement.org needs all CSS files to be minified and compressed as it can save up to 97.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 57 (46%)

Requests Now

123

After Optimization

66

The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tenement. 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 from 6 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

tenement.org accessibility score

72

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.

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

Buttons do not have an accessible name

High

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

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

tenement.org best practices score

75

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

tenement.org SEO score

86

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

robots.txt is not valid

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

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tenement.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Tenement.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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