Access hellonavi.jp. 【公式】静岡県のおすすめ観光スポット満載！ハローナビしずおか静岡県観光情報ホームページ

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value27.5 s

0/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value2,040 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value54.5 s

0/100

10%

hellonavi.jp

673 ms

default.css

327 ms

layout.css

653 ms

edit.css

659 ms

jquery.js

840 ms

Our browser made a total of 127 requests to load all elements on the main page. We found that 78% of them (99 requests) were addressed to the original Hellonavi.jp, 9% (12 requests) were made to Static.xx.fbcdn.net and 2% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Hellonavi.jp.

Content Size

17.0 MB

After Optimization

15.8 MB

In fact, the total size of Hellonavi.jp main page is 17.0 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. 75% 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 16.3 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 47.1 kB

Original 61.4 kB
After minification 61.0 kB
After compression 14.3 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 47.1 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 729.0 kB

Original 16.3 MB
After minification 15.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. Hellonavi images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 257.5 kB

Original 420.9 kB
After minification 353.7 kB
After compression 163.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 257.5 kB or 61% of the original size.

CSS Optimization

-87%

Potential reduce by 218.8 kB

Original 252.7 kB
After minification 190.8 kB
After compression 33.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. Hellonavi.jp needs all CSS files to be minified and compressed as it can save up to 218.8 kB or 87% of the original size.

Requests Now

124

After Optimization

The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hellonavi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 8 to 1 for CSS 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-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Document doesn't have a valid hreflang

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 uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

JA
Language Claimed

JA
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hellonavi.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Hellonavi.jp 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

hellonavi.jp

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

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

hellonavi.jp

default.css

layout.css

edit.css

jquery.js

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

hellonavi.jp

default.css

layout.css

edit.css

jquery.js

setting.js

ga.js

sdk.js

init.js

create_calendar.js

js

smartphone_search.js

crowdriff.js

utility.js

banner_rand_prev.js

slick_min.js

function.js

main.js

RssCommon.js

EventCommon.js

top.js

gtm.js

hanahaku-gardenparkmain.png

chatumi_w1160h488.png

fujisanmirunara_1160_488.jpg

ro-puway_w1160h488.png

slide_4.jpg

kawazubagatel-mainvisual.png

flowerparkmain0409.png

hanahaku_w1160h870.png

bnr_tips.jpg

harunozekkei_w1160h870.png

hanahaku2024-flowerpark0329.jpg

gardenpark0412.jpg

ususama-kasuisai-43.jpg

loading.gif

map.jpg

areamap_img_west.jpg

areamap_img_central.jpg

areamap_img_fuji.jpg

areamap_img_izu.jpg

tour_img1.jpg

nohakuguide-w1160h870.png

【公式】静岡県のおすすめ観光スポット満載！ハローナビしずおか静岡県観光情報ホームページ