Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

spongepark.org

Gowanus Canal Sponge Park™ Masterplan — DLANDstudio

Page Load Speed

285 ms in total

First Response

100 ms

Resources Loaded

102 ms

Page Rendered

83 ms

spongepark.org screenshot

About Website

Visit spongepark.org now to see the best up-to-date Sponge Park content and also check out these interesting facts you probably never knew about spongepark.org

Gowanus Canal Sponge Park™ Masterplan Location Brooklyn, New York Categories Research and Planning Parks and Infrastructure BackgroundFormerly a...

Visit spongepark.org

Key Findings

We analyzed Spongepark.org page load time and found that the first response time was 100 ms and then it took 185 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

spongepark.org performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.4 s

1/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value4,270 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.06

98/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

spongepark.org

100 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Spongepark.org and no external sources were called. The less responsive or slowest element that took the longest time to load (100 ms) belongs to the original domain Spongepark.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 18 B (12%)

Content Size

148 B

After Optimization

130 B

In fact, the total size of Spongepark.org main page is 148 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 148 B which makes up the majority of the site volume.

HTML Optimization

-12%

Potential reduce by 18 B

  • Original 148 B
  • After minification 147 B
  • After compression 130 B

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 18 B or 12% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

spongepark.org accessibility score

78

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

ARIA input fields do not have accessible names

High

ARIA toggle fields do not have accessible names

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

spongepark.org best practices score

83

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

SEO Factors

spongepark.org SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spongepark.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Spongepark.org main page’s claimed encoding is . 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 Sponge Park. 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: