Tools & Wizards About Us
lazecafe.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

lazecafe.com

Best Hookah Lounge Falls Church VA | Authentic Middle Eastern Restaurant Near Me

Page Load Speed

5.3 sec in total

First Response

189 ms

Resources Loaded

3.9 sec

Page Rendered

1.2 sec

lazecafe.com screenshot

About Website

Click here to check amazing Lazecafe content. Otherwise, check out these important facts you probably never knew about lazecafe.com

Falls Church's #1 rated hookah lounge & Middle Eastern restaurant. 50+ premium Al Fakher, Starbuzz & Adalya flavors. Authentic Lebanese cuisine, 98-inch 4K sports screens, late night dining until 2AM....

Visit lazecafe.com

Key Findings

We analyzed Lazecafe.com page load time and found that the first response time was 189 ms and then it took 5.2 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

lazecafe.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.4 s

0/100

25%

SI (Speed Index)

Value14.3 s

1/100

10%

TBT (Total Blocking Time)

Value1,100 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.188

65/100

15%

TTI (Time to Interactive)

Value27.6 s

0/100

10%

Network Requests Diagram

www.lazecafe.com

189 ms

wp-emoji-release.min.js

104 ms

common-skeleton.min.css

126 ms

tooltip.min.css

128 ms

style.min.css

128 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 79% of them (84 requests) were addressed to the original Lazecafe.com, 5% (5 requests) were made to Fonts.googleapis.com and 5% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (978 ms) belongs to the original domain Lazecafe.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 394.4 kB (3%)

Content Size

12.1 MB

After Optimization

11.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lazecafe.com main page is 12.1 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. Images take 10.9 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 116.6 kB

  • Original 143.3 kB
  • After minification 139.6 kB
  • After compression 26.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. 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 116.6 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 241.9 kB

  • Original 10.9 MB
  • After minification 10.6 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. Lazecafe images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 6.3 kB

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

-5%

Potential reduce by 29.5 kB

  • Original 593.4 kB
  • After minification 593.4 kB
  • After compression 564.0 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. Lazecafe.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 63 (63%)

Requests Now

100

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.lazecafe.com

www.lazecafe.com

189 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

104 ms

common-skeleton.min.css

common-skeleton.min.css

126 ms

tooltip.min.css

tooltip.min.css

128 ms

style.min.css

style.min.css

128 ms

styles.css

styles.css

130 ms

jquery-ui.min.css

jquery-ui.min.css

20 ms

jquery-ui-timepicker-addon.min.css

jquery-ui-timepicker-addon.min.css

129 ms

settings.css

settings.css

168 ms

css

css

19 ms

css

css

22 ms

css

css

22 ms

fontello.css

fontello.css

192 ms

exitintentpopup.css

exitintentpopup.css

193 ms

vtaa_popupstyle.css

vtaa_popupstyle.css

197 ms

animate.css

animate.css

195 ms

rs6.css

rs6.css

200 ms

trx_addons_icons-embedded.css

trx_addons_icons-embedded.css

353 ms

swiper.min.css

swiper.min.css

256 ms

magnific-popup.min.css

magnific-popup.min.css

259 ms

trx_addons.css

trx_addons.css

401 ms

js_composer.min.css

js_composer.min.css

387 ms

css

css

20 ms

fontello-embedded.css

fontello-embedded.css

518 ms

style.css

style.css

449 ms

__colors.css

__colors.css

412 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

425 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

461 ms

trx_addons.responsive.css

trx_addons.responsive.css

461 ms

responsive.css

responsive.css

465 ms

jquery.js

jquery.js

488 ms

jquery-migrate.min.js

jquery-migrate.min.js

514 ms

exitintentpopup.js

exitintentpopup.js

517 ms

vt-textcookie.js

vt-textcookie.js

544 ms

revolution.tools.min.js

revolution.tools.min.js

545 ms

rs6.min.js

rs6.min.js

575 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

586 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

581 ms

css

css

31 ms

jquery.esgbox.min.css

jquery.esgbox.min.css

548 ms

scripts.js

scripts.js

549 ms

core.min.js

core.min.js

633 ms

datepicker.min.js

datepicker.min.js

634 ms

jquery-ui-timepicker-addon.min.js

jquery-ui-timepicker-addon.min.js

569 ms

widget.min.js

widget.min.js

547 ms

mouse.min.js

mouse.min.js

545 ms

slider.min.js

slider.min.js

546 ms

button.min.js

button.min.js

578 ms

jquery-ui-sliderAccess.js

jquery-ui-sliderAccess.js

628 ms

swiper.jquery.min.js

swiper.jquery.min.js

646 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

621 ms

trx_addons.js

trx_addons.js

621 ms

superfish.min.js

superfish.min.js

618 ms

__scripts.js

__scripts.js

616 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

614 ms

wp-embed.min.js

wp-embed.min.js

572 ms

js_composer_front.min.js

js_composer_front.min.js

568 ms

skrollr.min.js

skrollr.min.js

525 ms

jquery.themepunch.essential.min.js

jquery.themepunch.essential.min.js

484 ms

jquery.esgbox.min.js

jquery.esgbox.min.js

458 ms

Laze-Final-Logo-Black-Background-01.jpg

Laze-Final-Logo-Black-Background-01.jpg

363 ms

Laze-Final-Logo-Black-Background-01-1-300x122.jpg

Laze-Final-Logo-Black-Background-01-1-300x122.jpg

317 ms

gallery-3.jpg

gallery-3.jpg

719 ms

bg-6.jpg

bg-6.jpg

364 ms

gallery-5-1.jpg

gallery-5-1.jpg

419 ms

slider_1.jpg

slider_1.jpg

418 ms

IMG_1013.jpg

IMG_1013.jpg

566 ms

20190906_133322-1.jpg

20190906_133322-1.jpg

426 ms

image-9.jpg

image-9.jpg

491 ms

Laze_10.jpg

Laze_10.jpg

530 ms

gallery-6.jpg

gallery-6.jpg

474 ms

image-9.jpg

image-9.jpg

491 ms

gallery-5.jpg

gallery-5.jpg

538 ms

image-4.jpg

image-4.jpg

555 ms

12346089_922543737794119_1989434543_a-1.jpg

12346089_922543737794119_1989434543_a-1.jpg

555 ms

bg-14.jpg

bg-14.jpg

534 ms

image-900.jpg

image-900.jpg

542 ms

bg-3.jpg

bg-3.jpg

556 ms

9Y6C0057-.jpg

9Y6C0057-.jpg

978 ms

image-9-1170x658.jpg

image-9-1170x658.jpg

623 ms

9Y6C0057--1170x658.jpg

9Y6C0057--1170x658.jpg

659 ms

home-8-masonry-gallery-3-550x550.jpg

home-8-masonry-gallery-3-550x550.jpg

603 ms

bg-6.jpg

bg-6.jpg

587 ms

font

font

217 ms

font

font

250 ms

DewXAiKGIjI2Nf5AbGnRwMHAzJBRsZWJ02MTAyaIEYm7mYGDkgLD4GMIvNaRfTAaA0J5DN7rSLwQHCZmZw2ajC2BEYscGhI2Ijc4rLRjUQbxdHAwMji0NHckgESEkkEGzmYWLk0drB+L91A0vvRiYGFwAMdiP0AAA=

DewXAiKGIjI2Nf5AbGnRwMHAzJBRsZWJ02MTAyaIEYm7mYGDkgLD4GMIvNaRfTAaA0J5DN7rSLwQHCZmZw2ajC2BEYscGhI2Ijc4rLRjUQbxdHAwMji0NHckgESEkkEGzmYWLk0drB+L91A0vvRiYGFwAMdiP0AAA=

39 ms

fontello.svg

fontello.svg

636 ms

DewXAiKGIjI2Nf5AbGnRwMHAzJBRsZWJ02MTAyaIEYm7mYGDkgLD4GMIvNaRfTAaA0J5DN7rSLwQHCZmZw2ajC2BEYscGhI2Ijc4rLRjUQbxdHAwMji0NHckgESEkkEGzmYWLk0drB+L91A0vvRiYGFwAMdiP0AAA=

DewXAiKGIjI2Nf5AbGnRwMHAzJBRsZWJ02MTAyaIEYm7mYGDkgLD4GMIvNaRfTAaA0J5DN7rSLwQHCZmZw2ajC2BEYscGhI2Ijc4rLRjUQbxdHAwMji0NHckgESEkkEGzmYWLk0drB+L91A0vvRiYGFwAMdiP0AAA=

36 ms

trx_addons_icons.svg

trx_addons_icons.svg

619 ms

bg-8.jpg

bg-8.jpg

565 ms

bg_1.jpg

bg_1.jpg

694 ms

image-5-770x443.jpg

image-5-770x443.jpg

605 ms

bg-13.jpg

bg-13.jpg

612 ms

embed

embed

396 ms

2615.svg

2615.svg

23 ms

bg_footer-1.jpg

bg_footer-1.jpg

509 ms

2764.svg

2764.svg

11 ms

font

font

75 ms

font

font

16 ms

font

font

74 ms

iframe_api

iframe_api

101 ms

www-widgetapi.js

www-widgetapi.js

3 ms

js

js

29 ms

search.js

search.js

4 ms

geometry.js

geometry.js

7 ms

main.js

main.js

12 ms

Accessibility Review

lazecafe.com accessibility score

69

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

Buttons do not have an accessible name

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

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

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

lazecafe.com best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

lazecafe.com SEO score

77

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

lazecafe.com

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