Tools & Wizards About Us
saywhatnyc.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

saywhatnyc.com

Say What? NYC Comedy Improv

Page Load Speed

2.5 sec in total

First Response

137 ms

Resources Loaded

2.3 sec

Page Rendered

51 ms

saywhatnyc.com screenshot

About Website

Visit saywhatnyc.com now to see the best up-to-date Say What NYC content and also check out these interesting facts you probably never knew about saywhatnyc.com

NYC's best short-form improv group!

Visit saywhatnyc.com

Key Findings

We analyzed Saywhatnyc.com page load time and found that the first response time was 137 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

saywhatnyc.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value15.1 s

1/100

10%

TBT (Total Blocking Time)

Value3,820 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value22.5 s

1/100

10%

Network Requests Diagram

www.saywhatnyc.com

137 ms

minified.js

41 ms

focus-within-polyfill.js

40 ms

polyfill.min.js

1166 ms

mobile-app-invite-banner.css

71 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Saywhatnyc.com, 28% (12 requests) were made to Sentry-next.wixpress.com and 28% (12 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 513.3 kB (37%)

Content Size

1.4 MB

After Optimization

876.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Saywhatnyc.com main page is 1.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. HTML takes 532.1 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 416.8 kB

  • Original 532.1 kB
  • After minification 530.5 kB
  • After compression 115.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 416.8 kB or 78% of the original size.

Image Optimization

-27%

Potential reduce by 89.6 kB

  • Original 326.8 kB
  • After minification 237.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. Obviously, Say What NYC needs image optimization as it can save up to 89.6 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 6.8 kB

  • Original 468.8 kB
  • After minification 468.8 kB
  • After compression 462.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 56 B

  • Original 61.9 kB
  • After minification 61.9 kB
  • After compression 61.8 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. Saywhatnyc.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (42%)

Requests Now

38

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.saywhatnyc.com

www.saywhatnyc.com

137 ms

minified.js

minified.js

41 ms

focus-within-polyfill.js

focus-within-polyfill.js

40 ms

polyfill.min.js

polyfill.min.js

1166 ms

mobile-app-invite-banner.css

mobile-app-invite-banner.css

71 ms

mobile-app-invite-banner.umd.min.js

mobile-app-invite-banner.umd.min.js

73 ms

thunderbolt-commons.e7839053.bundle.min.js

thunderbolt-commons.e7839053.bundle.min.js

63 ms

main.760485a2.bundle.min.js

main.760485a2.bundle.min.js

54 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

51 ms

lodash.min.js

lodash.min.js

53 ms

react.production.min.js

react.production.min.js

52 ms

react-dom.production.min.js

react-dom.production.min.js

54 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

53 ms

web_logo_edited_edited.png

web_logo_edited_edited.png

540 ms

035244_6f75c90bfd8b4f9eac84808fe7afcc92~mv2.png

035244_6f75c90bfd8b4f9eac84808fe7afcc92~mv2.png

584 ms

035244_7a6c06171f9a414baf5c990ce9f840ad~mv2.png

035244_7a6c06171f9a414baf5c990ce9f840ad~mv2.png

590 ms

X7vR54qa7N0

X7vR54qa7N0

173 ms

ironpatern.84ec58ff.png

ironpatern.84ec58ff.png

70 ms

bundle.min.js

bundle.min.js

68 ms

403 ms

399 ms

398 ms

396 ms

396 ms

389 ms

443 ms

437 ms

433 ms

437 ms

436 ms

435 ms

www-player.css

www-player.css

17 ms

www-embed-player.js

www-embed-player.js

43 ms

base.js

base.js

74 ms

ad_status.js

ad_status.js

198 ms

LBEmR2h8SoU0Qas6GEfhRoA0j2cP-KYEH279PJ_PFPQ.js

LBEmR2h8SoU0Qas6GEfhRoA0j2cP-KYEH279PJ_PFPQ.js

127 ms

embed.js

embed.js

61 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

106 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

106 ms

Create

Create

88 ms

id

id

79 ms

qoe

qoe

12 ms

log_event

log_event

1 ms

Accessibility Review

saywhatnyc.com accessibility score

94

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

saywhatnyc.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

saywhatnyc.com SEO score

99

Search Engine Optimization Advices

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

saywhatnyc.com

Open Graph data is detected on the main page of Say What NYC. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: