Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

cafeginger.net

Chinese Cuisine & Sushi Bar | Cafe Ginger River Oaks | United States

Page Load Speed

647 ms in total

First Response

55 ms

Resources Loaded

538 ms

Page Rendered

54 ms

cafeginger.net screenshot

About Website

Click here to check amazing Cafe Ginger content. Otherwise, check out these important facts you probably never knew about cafeginger.net

Cafe Ginger, located in the Galleria/Uptown neighborhood of Houston, is one of the city’s best casual elegant restaurants. The Japanese-Chinese fusion appeals to locals and visitors alike and the upsc...

Visit cafeginger.net

Key Findings

We analyzed Cafeginger.net page load time and found that the first response time was 55 ms and then it took 592 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

cafeginger.net performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.202

61/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

www.cafeginger.net

55 ms

minified.js

29 ms

focus-within-polyfill.js

63 ms

polyfill.min.js

28 ms

thunderbolt-commons.7700cd07.bundle.min.js

102 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Cafeginger.net, 41% (12 requests) were made to Static.parastorage.com and 41% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (288 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 359.6 kB (50%)

Content Size

713.5 kB

After Optimization

353.9 kB

In fact, the total size of Cafeginger.net main page is 713.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. HTML takes 407.5 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 311.5 kB

  • Original 407.5 kB
  • After minification 405.8 kB
  • After compression 96.0 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 311.5 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.5 kB
  • After minification 2.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. Cafe Ginger images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 48.1 kB

  • Original 303.5 kB
  • After minification 303.5 kB
  • After compression 255.4 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 48.1 kB or 16% of the original size.

Requests Breakdown

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

Requests Now

16

After Optimization

6

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

Accessibility Review

cafeginger.net accessibility score

98

Accessibility Issues

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

cafeginger.net best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

cafeginger.net SEO score

100

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

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 Cafeginger.net 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 Cafeginger.net 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

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