Tools & Wizards About Us
longstreethotel.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

longstreethotel.com

Cape Town Central Hotel | Long Street Hotel

Page Load Speed

6.5 sec in total

First Response

810 ms

Resources Loaded

5.3 sec

Page Rendered

348 ms

longstreethotel.com screenshot

About Website

Visit longstreethotel.com now to see the best up-to-date Long Street Hotel content and also check out these interesting facts you probably never knew about longstreethotel.com

Cape Town Accommodation - Find and book luxury accommodation on the famous Long Street Strip in the heart of the city at Long Street Hotel, Cape Town

Visit longstreethotel.com

Key Findings

We analyzed Longstreethotel.com page load time and found that the first response time was 810 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

longstreethotel.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value1,850 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.298

40/100

15%

TTI (Time to Interactive)

Value15.6 s

6/100

10%

Network Requests Diagram

longstreethotel.com

810 ms

main.css

260 ms

mediaqueries.css

508 ms

camera.css

519 ms

jquery.min.js

826 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 58% of them (47 requests) were addressed to the original Longstreethotel.com, 15% (12 requests) were made to Maps.googleapis.com and 6% (5 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Longstreethotel.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (48%)

Content Size

2.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Longstreethotel.com main page is 2.3 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. 65% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 14.9 kB

  • Original 19.4 kB
  • After minification 17.0 kB
  • After compression 4.5 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 2.3 kB, which is 12% 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 14.9 kB or 77% of the original size.

Image Optimization

-5%

Potential reduce by 39.4 kB

  • Original 794.9 kB
  • After minification 755.5 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. Long Street Hotel images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 754.9 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 349.8 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 754.9 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 282.5 kB

  • Original 339.4 kB
  • After minification 325.2 kB
  • After compression 56.9 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. Longstreethotel.com needs all CSS files to be minified and compressed as it can save up to 282.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (45%)

Requests Now

75

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

longstreethotel.com

longstreethotel.com

810 ms

main.css

main.css

260 ms

mediaqueries.css

mediaqueries.css

508 ms

camera.css

camera.css

519 ms

jquery.min.js

jquery.min.js

826 ms

jquery.mobile.customized.min.js

jquery.mobile.customized.min.js

524 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

523 ms

camera.min.js

camera.min.js

522 ms

jquery-ui.min.js

jquery-ui.min.js

16 ms

jquery-mobilemenu.min.js

jquery-mobilemenu.min.js

758 ms

custom.js

custom.js

775 ms

layout.css

layout.css

523 ms

pages.css

pages.css

525 ms

elements.css

elements.css

525 ms

framework.css

framework.css

752 ms

stylesheet.css

stylesheet.css

773 ms

font-awesome.min.css

font-awesome.min.css

781 ms

custom.css

custom.css

782 ms

demo-only.css

demo-only.css

782 ms

analytics.js

analytics.js

19 ms

bk.jpg

bk.jpg

1586 ms

WweXixz44_A

WweXixz44_A

135 ms

embed

embed

232 ms

tel.png

tel.png

295 ms

twitter.png

twitter.png

295 ms

facebook.png

facebook.png

296 ms

logo.jpg

logo.jpg

294 ms

dropdown_side.gif

dropdown_side.gif

294 ms

img1.jpg

img1.jpg

1362 ms

book-now.png

book-now.png

583 ms

1.jpg

1.jpg

583 ms

2.jpg

2.jpg

800 ms

facebook-icon.png

facebook-icon.png

583 ms

foursq.png

foursq.png

846 ms

trip-advisor-png.png

trip-advisor-png.png

843 ms

1.png

1.png

844 ms

2.png

2.png

1050 ms

collect

collect

60 ms

camera_skins.png

camera_skins.png

1242 ms

camera-loader.gif

camera-loader.gif

986 ms

3.jpg

3.jpg

985 ms

8.jpg

8.jpg

1185 ms

17.jpg

17.jpg

1246 ms

12.jpg

12.jpg

1244 ms

19.jpg

19.jpg

1437 ms

13.jpg

13.jpg

1500 ms

15.jpg

15.jpg

1499 ms

30.jpg

30.jpg

1502 ms

29.jpg

29.jpg

1504 ms

slide3.jpg

slide3.jpg

2449 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

22 ms

www-embed-player.js

www-embed-player.js

42 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

27 ms

ad_status.js

ad_status.js

91 ms

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

83 ms

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

86 ms

js

js

133 ms

init_embed.js

init_embed.js

91 ms

common.js

common.js

71 ms

map.js

map.js

71 ms

google4.png

google4.png

85 ms

overlay.js

overlay.js

14 ms

util.js

util.js

96 ms

onion.js

onion.js

76 ms

search_impl.js

search_impl.js

93 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

159 ms

stats.js

stats.js

91 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

66 ms

transparent.png

transparent.png

50 ms

kh

kh

77 ms

controls.js

controls.js

28 ms

css

css

68 ms

vt

vt

78 ms

vt

vt

89 ms

vt

vt

53 ms

mapcnt6.png

mapcnt6.png

30 ms

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

3 ms

d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf

d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf

8 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

26 ms

index.php

index.php

779 ms

slide8.jpg

slide8.jpg

818 ms

Accessibility Review

longstreethotel.com accessibility score

86

Accessibility Issues

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

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

High

Image elements do not have [alt] attributes

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

Best Practices

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

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

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

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 Longstreethotel.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 Longstreethotel.com main page’s claimed encoding is utf-8;. 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

longstreethotel.com

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