Tools & Wizards About Us
sweetpollynyc.com screenshot

Report Summary

  • 81

    Performance

    Renders faster than
    87% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

sweetpollynyc.com

Sweet Polly

Page Load Speed

866 ms in total

First Response

13 ms

Resources Loaded

489 ms

Page Rendered

364 ms

sweetpollynyc.com screenshot

About Website

Visit sweetpollynyc.com now to see the best up-to-date Sweet Polly Nyc content and also check out these interesting facts you probably never knew about sweetpollynyc.com

Cozy-chic bar for cocktails (plus wines & New York beers) with oysters, cheeses & small plates.

Visit sweetpollynyc.com

Key Findings

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

Performance Metrics

sweetpollynyc.com performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value2.9 s

96/100

10%

Network Requests Diagram

sweetpollynyc.com

13 ms

www.sweetpollynyc.com

25 ms

head.min.js

50 ms

main.1139ad9f90183b87e365dfa94d9025f3.scss

117 ms

foot.libs.min.js

71 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Sweetpollynyc.com, 55% (18 requests) were made to Images.getbento.com and 12% (4 requests) were made to Theme-assets.getbento.com. The less responsive or slowest element that took the longest time to load (227 ms) relates to the external source App-assets.getbento.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 37.6 kB (2%)

Content Size

2.5 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sweetpollynyc.com main page is 2.5 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. 50% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 34.1 kB

  • Original 40.8 kB
  • After minification 35.0 kB
  • After compression 6.7 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 5.9 kB, which is 14% 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 34.1 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 2.9 kB

  • 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. Sweet Polly Nyc images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 16 B

  • Original 709.7 kB
  • After minification 709.7 kB
  • After compression 709.7 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

-2%

Potential reduce by 550 B

  • Original 34.3 kB
  • After minification 34.3 kB
  • After compression 33.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. Sweetpollynyc.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 4 (14%)

Requests Now

28

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sweetpollynyc.com

sweetpollynyc.com

13 ms

www.sweetpollynyc.com

www.sweetpollynyc.com

25 ms

head.min.js

head.min.js

50 ms

main.1139ad9f90183b87e365dfa94d9025f3.scss

main.1139ad9f90183b87e365dfa94d9025f3.scss

117 ms

foot.libs.min.js

foot.libs.min.js

71 ms

bentobox.min.js

bentobox.min.js

110 ms

main.js

main.js

91 ms

main.js.map

main.js.map

227 ms

bento-analytics.min.js

bento-analytics.min.js

88 ms

60df9091-5246-4ca5-bd8e-1ba125f2aa5a.js

60df9091-5246-4ca5-bd8e-1ba125f2aa5a.js

205 ms

css

css

64 ms

42426Texture0204.jpg

42426Texture0204.jpg

144 ms

hRvNbZ3USny0f7dj6mwg_logo-white.png

hRvNbZ3USny0f7dj6mwg_logo-white.png

49 ms

24240M_Cooper_2017_Sweet_Polly_00053.jpg

24240M_Cooper_2017_Sweet_Polly_00053.jpg

111 ms

7O54XANzRg6g9OvnEFGp_M%20Cooper%202017%20Sweet%20Polly%2000086.jpg

7O54XANzRg6g9OvnEFGp_M%20Cooper%202017%20Sweet%20Polly%2000086.jpg

57 ms

9053DSC_3302_1.jpg

9053DSC_3302_1.jpg

54 ms

3F68JebTu63kWlYIfDTw_M%20Cooper%202017%20Sweet%20Polly%2000166.jpg

3F68JebTu63kWlYIfDTw_M%20Cooper%202017%20Sweet%20Polly%2000166.jpg

60 ms

66491M_Cooper_x_Sweet_Polly_Editorial_2017-09-05_25.jpg

66491M_Cooper_x_Sweet_Polly_Editorial_2017-09-05_25.jpg

55 ms

xmnAFncZTKm8WEsnBC0i__MG_0155.jpg

xmnAFncZTKm8WEsnBC0i__MG_0155.jpg

115 ms

18386___M_Cooper_20210311_Sweet_Polly_Outdoor_Seating_19_1.jpg

18386___M_Cooper_20210311_Sweet_Polly_Outdoor_Seating_19_1.jpg

69 ms

1sdsXzRTinLhebPOvA0w_MCP%20SP%202018Q3%20Jazz%20Cartel%2002.jpg

1sdsXzRTinLhebPOvA0w_MCP%20SP%202018Q3%20Jazz%20Cartel%2002.jpg

61 ms

31761M_Cooper_20210311_Sweet_Polly_Outdoor_Seating_02.jpg

31761M_Cooper_20210311_Sweet_Polly_Outdoor_Seating_02.jpg

123 ms

ZLF3DdtBSNWPizcKXoKa_Vertical.jpg

ZLF3DdtBSNWPizcKXoKa_Vertical.jpg

81 ms

33720Screen_Shot_2019-01-25_at_3.51.30_PM.png

33720Screen_Shot_2019-01-25_at_3.51.30_PM.png

121 ms

16179_MG_0167.2.jpg

16179_MG_0167.2.jpg

136 ms

mvKF3jl1TfyOWuGvN8eF_M%20Cooper%202017%20Sweet%20Polly%2000044.jpg

mvKF3jl1TfyOWuGvN8eF_M%20Cooper%202017%20Sweet%20Polly%2000044.jpg

146 ms

13665_M_Cooper_20210311_Sweet_Polly_Outdoor_Seating_17.jpg

13665_M_Cooper_20210311_Sweet_Polly_Outdoor_Seating_17.jpg

175 ms

86084MC_Sweet_Polly_071.jpg

86084MC_Sweet_Polly_071.jpg

179 ms

80414bgcolor.png

80414bgcolor.png

185 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMZhKg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMZhKg.ttf

30 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_N_XbMZhKg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_N_XbMZhKg.ttf

29 ms

font-bento-custom.woff

font-bento-custom.woff

15 ms

mt.js

mt.js

18 ms

Accessibility Review

sweetpollynyc.com accessibility score

100

Accessibility Issues

Best Practices

sweetpollynyc.com 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

High

Missing source maps for large first-party JavaScript

SEO Factors

sweetpollynyc.com SEO score

93

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sweetpollynyc.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 Sweetpollynyc.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

sweetpollynyc.com

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