Tools & Wizards About Us
loreleynyc.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

loreleynyc.com

Loreley Beer Garden | Restaurant, Heated Outdoor Beer Garden, Beer Hall, Bar & Lounge in New York, NY

Page Load Speed

1.9 sec in total

First Response

142 ms

Resources Loaded

1.4 sec

Page Rendered

424 ms

loreleynyc.com screenshot

About Website

Welcome to loreleynyc.com homepage info - get ready to check Loreley NY C best content for United States right away, or after learning these important things about loreleynyc.com

Restaurants, Beer Garden, Outdoor Dining, Open Restaurants, Heated Dining, Cocktails, Bars, Lounge, Beer, Craft Beer, Local Beer, Private Events, Party Room NYC

Visit loreleynyc.com

Key Findings

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

Performance Metrics

loreleynyc.com performance score

0

Network Requests Diagram

loreleynyc.com

142 ms

loreley-style.css

44 ms

buttons.js

8 ms

loader.js

6 ms

snapwidget.js

22 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 33% of them (32 requests) were addressed to the original Loreleynyc.com, 7% (7 requests) were made to W.sharethis.com and 6% (6 requests) were made to Snapwidget.com. The less responsive or slowest element that took the longest time to load (561 ms) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 550.4 kB (16%)

Content Size

3.5 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 18.4 kB

  • Original 25.2 kB
  • After minification 24.5 kB
  • After compression 6.8 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 18.4 kB or 73% of the original size.

Image Optimization

-7%

Potential reduce by 211.2 kB

  • Original 3.0 MB
  • After minification 2.8 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. Loreley NY C images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 241.7 kB

  • Original 372.4 kB
  • After minification 372.3 kB
  • After compression 130.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 241.7 kB or 65% of the original size.

CSS Optimization

-81%

Potential reduce by 79.2 kB

  • Original 97.3 kB
  • After minification 95.4 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. Loreleynyc.com needs all CSS files to be minified and compressed as it can save up to 79.2 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (41%)

Requests Now

93

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

loreleynyc.com

loreleynyc.com

142 ms

loreley-style.css

loreley-style.css

44 ms

buttons.js

buttons.js

8 ms

loader.js

loader.js

6 ms

snapwidget.js

snapwidget.js

22 ms

fbevents.js

fbevents.js

157 ms

sdk.js

sdk.js

345 ms

instagram_header.png

instagram_header.png

195 ms

82 ms

events.php

events.php

169 ms

getAllAppDefault.esi

getAllAppDefault.esi

127 ms

graphic_loreley.jpg

graphic_loreley.jpg

82 ms

stpats_poster.jpg

stpats_poster.jpg

420 ms

amnesia1319.png

amnesia1319.png

529 ms

doghaus.png

doghaus.png

461 ms

logo.jpg

logo.jpg

82 ms

news.jpg

news.jpg

107 ms

drinks_header.jpg

drinks_header.jpg

134 ms

drinks_beer.jpg

drinks_beer.jpg

134 ms

drinks_wine.jpg

drinks_wine.jpg

146 ms

menus_header.jpg

menus_header.jpg

166 ms

menus_brunch.jpg

menus_brunch.jpg

168 ms

menus_manhattan.jpg

menus_manhattan.jpg

193 ms

menus_williamsburg.jpg

menus_williamsburg.jpg

225 ms

locations.jpg

locations.jpg

226 ms

photos.jpg

photos.jpg

244 ms

about.jpg

about.jpg

269 ms

news_hover.jpg

news_hover.jpg

268 ms

drinks_beer_hover.jpg

drinks_beer_hover.jpg

287 ms

drinks_wine_hover.jpg

drinks_wine_hover.jpg

360 ms

menus_manhattan_hover.jpg

menus_manhattan_hover.jpg

358 ms

menus_williamsburg_hover.jpg

menus_williamsburg_hover.jpg

357 ms

menus_brunch_hover.jpg

menus_brunch_hover.jpg

386 ms

locations_hover.jpg

locations_hover.jpg

387 ms

photos_hover.jpg

photos_hover.jpg

389 ms

about_hover.jpg

about_hover.jpg

429 ms

icon_twitter.jpg

icon_twitter.jpg

431 ms

icon_facebook.jpg

icon_facebook.jpg

451 ms

mailinglist.jpg

mailinglist.jpg

473 ms

lore_btn.jpg

lore_btn.jpg

473 ms

combined.css

combined.css

7 ms

smoothDivScroll.css

smoothDivScroll.css

4 ms

stack_161235.js

stack_161235.js

49 ms

iframeresize.js

iframeresize.js

4 ms

jquery.min.js

jquery.min.js

12 ms

analytics.js

analytics.js

23 ms

stackpile.api-bfb5078e74.js

stackpile.api-bfb5078e74.js

24 ms

12784073_264721297192145_1934642241_n.jpg

12784073_264721297192145_1934642241_n.jpg

286 ms

small_share_sprite.png

small_share_sprite.png

22 ms

12797910_1711173292489450_317955396_n.jpg

12797910_1711173292489450_317955396_n.jpg

417 ms

12751630_934721339977428_826358028_n.jpg

12751630_934721339977428_826358028_n.jpg

477 ms

12383482_965151883533630_687349927_n.jpg

12383482_965151883533630_687349927_n.jpg

491 ms

stackpile.api-bfb5078e74.js

stackpile.api-bfb5078e74.js

17 ms

117 ms

collect

collect

14 ms

collect

collect

59 ms

dialog.css

dialog.css

13 ms

jquery.min.js

jquery.min.js

63 ms

jquery-ui.min.js

jquery-ui.min.js

82 ms

getSegment.php

getSegment.php

231 ms

checkOAuth.esi

checkOAuth.esi

62 ms

ga.js

ga.js

15 ms

like.php

like.php

82 ms

t.dhj

t.dhj

26 ms

pixel

pixel

23 ms

40 ms

94 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

497 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

561 ms

xd_arbiter.php

xd_arbiter.php

221 ms

xd_arbiter.php

xd_arbiter.php

428 ms

pixel

pixel

14 ms

t.dhj

t.dhj

29 ms

10400976_23400490838_5443_n.jpg

10400976_23400490838_5443_n.jpg

280 ms

adxmapping.php

adxmapping.php

78 ms

cm

cm

16 ms

s-3271.xgi

s-3271.xgi

21 ms

hbpix

hbpix

47 ms

19 ms

15 ms

hoverbuttons.6eab8de2ee93b309873157b6d3f977fe.css

hoverbuttons.6eab8de2ee93b309873157b6d3f977fe.css

26 ms

hoverbuttons.035267d71d894482eb413e5bea488ff5.js

hoverbuttons.035267d71d894482eb413e5bea488ff5.js

28 ms

xrefid.xgi

xrefid.xgi

8 ms

pixel

pixel

12 ms

2981

2981

23 ms

nr-885.min.js

nr-885.min.js

16 ms

a53393d12f

a53393d12f

44 ms

buttons.ab966a004186897711de4a5ed256c924.css

buttons.ab966a004186897711de4a5ed256c924.css

31 ms

mini_Top_Cap.png

mini_Top_Cap.png

21 ms

__utm.gif

__utm.gif

11 ms

mini_BG.png

mini_BG.png

6 ms

mini_Bottom_Cap.png

mini_Bottom_Cap.png

7 ms

facebook_32.png

facebook_32.png

7 ms

twitter_32.png

twitter_32.png

7 ms

instagram_32.png

instagram_32.png

7 ms

pinterest_32.png

pinterest_32.png

8 ms

email_32.png

email_32.png

8 ms

xd_arbiter.php

xd_arbiter.php

137 ms

SEO Factors

loreleynyc.com SEO score

0

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

loreleynyc.com

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