Access snacknavi.com. 全日本スナックナビ東京

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value1,360 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.641

9/100

15%

TTI (Time to Interactive)

Value10.0 s

27/100

10%

snacknavi.com

1386 ms

text.css

564 ms

roll.js

387 ms

ga.js

65 ms

back.gif

203 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 79% of them (94 requests) were addressed to the original Snacknavi.com, 11% (13 requests) were made to Pbs.twimg.com and 3% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Snacknavi.com.

Content Size

1.8 MB

After Optimization

1.7 MB

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

HTML Optimization

-84%

Potential reduce by 50.1 kB

Original 59.9 kB
After minification 52.5 kB
After compression 9.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. This page needs HTML code to be minified as it can gain 7.4 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 50.1 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 54.3 kB

Original 1.7 MB
After minification 1.7 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. Snacknavi images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 647 B

Original 18.2 kB
After minification 18.1 kB
After compression 17.6 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

-83%

Potential reduce by 9.5 kB

Original 11.5 kB
After minification 9.3 kB
After compression 1.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. Snacknavi.com needs all CSS files to be minified and compressed as it can save up to 9.5 kB or 83% of the original size.

Requests Now

116

After Optimization

112

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA input fields do not have accessible names

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

Form elements do not have associated labels

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

JA
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Snacknavi.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Snacknavi.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

snacknavi.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

全日本スナックナビ東京｜全日本スナックナビ

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

snacknavi.com

text.css

roll.js

ga.js

back.gif

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

snacknavi.com

text.css

roll.js

ga.js

back.gif

header_back2.gif

zen_logo.gif

zen_tab01.gif

zen_tab02.gif

zen_tab03.gif

zen_tab04.gif

zen_tab05.gif

zen_tab06.gif

zen_tab07.gif

zen_tab08.gif

logo.gif

header.gif

banner_blog.gif

menu01a.gif

menu02a.gif

menu03a.gif

menu04a.gif

menu05a.gif

menu06a.gif

sub01a.gif

sub02a.gif

sub_back.gif

sub_icon.gif

sub_bt.gif

map_menu01.gif

map_menu03.gif

map_td01.gif

map_td02.gif

map_stationback.gif

map.gif

map_td03.gif

725x170_PC.jpg

ishibashi_img01.gif

bn_CP.gif

top_about.gif

widgets.js

__utm.gif

timeline.1b43d11859b7663a2225b885f87704a5.js