Access crazyfiregrillandsushi.com.

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

42/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value4.3 s

84/100

10%

crazyfiregrillandsushi.com

226 ms

ww25.crazyfiregrillandsushi.com

82 ms

bPqEoePYg.js

3 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that 33% of them (1 request) were addressed to the original Crazyfiregrillandsushi.com, 67% (2 requests) were made to Ww25.crazyfiregrillandsushi.com. The less responsive or slowest element that took the longest time to load (226 ms) belongs to the original domain Crazyfiregrillandsushi.com.

Content Size

1.2 kB

After Optimization

831 B

In fact, the total size of Crazyfiregrillandsushi.com main page is 1.2 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. Only 5% of websites need less resources to load. HTML takes 1.2 kB which makes up the majority of the site volume.

HTML Optimization

-31%

Potential reduce by 380 B

Original 1.2 kB
After minification 1.2 kB
After compression 831 B

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 380 B or 31% of the original size.

Requests Now

After Optimization

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Crazyfiregrillandsushi. According to our analytics all requests are already optimized.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Page is blocked from indexing

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/).

High

Document doesn't use legible font sizes

Language and Encoding

Language Detected

N/A
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Crazyfiregrillandsushi.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Crazyfiregrillandsushi.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

crazyfiregrillandsushi.com

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