Access hatsushima.jp. 初島に行こうよ【公式】熱海から30分のリゾートアイランド

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value1,030 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value1.001

2/100

15%

TTI (Time to Interactive)

Value20.2 s

2/100

10%

hatsushima.jp

547 ms

hatsushima.jp

973 ms

gtm.js

66 ms

default.css

934 ms

common.css

1354 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 77% of them (62 requests) were addressed to the original Hatsushima.jp, 4% (3 requests) were made to Googletagmanager.com and 4% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Hatsushima.jp.

Content Size

2.9 MB

After Optimization

2.6 MB

In fact, the total size of Hatsushima.jp main page is 2.9 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 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 35.5 kB

Original 46.4 kB
After minification 41.1 kB
After compression 10.9 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 5.2 kB, which is 11% 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 35.5 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 51.9 kB

Original 2.6 MB
After minification 2.5 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. Hatsushima images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 76.8 kB

Original 147.6 kB
After minification 144.2 kB
After compression 70.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 76.8 kB or 52% of the original size.

CSS Optimization

-88%

Potential reduce by 96.9 kB

Original 110.2 kB
After minification 85.2 kB
After compression 13.3 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. Hatsushima.jp needs all CSS files to be minified and compressed as it can save up to 96.9 kB or 88% of the original size.

Requests Now

After Optimization

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

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 interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

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

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

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

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

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Image elements do not have [alt] attributes

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

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hatsushima.jp 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 Hatsushima.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

hatsushima.jp

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

初島に行こうよ【公式】熱海から30分のリゾートアイランド

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

hatsushima.jp

hatsushima.jp

gtm.js

default.css

common.css

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

hatsushima.jp

hatsushima.jp

gtm.js

default.css

common.css

font-awesome.min.css

homepage.css

magnific-popup.css

jquery-2.1.4.min.js

config.js

common.js

homepage.js

jquery.magnific-popup.min.js

js

analytics.js

destination

uwt.js

collect

collect

adsct

adsct

ytag.js

ga-audiences

btn_scroll.png

logo_lower.png

bn_lemonfes.jpg

bn_lp.jpg

bn_snaplace.jpg

jyoshitabi.jpg

bn_map.jpg

bg_bnav.png

bg_fer.png

btn_plan.png

hr_gui.png

img_gui4.jpg

img_gui1.jpg

img_gui3.jpg

img_gui5.jpg

img_gui6_2.jpg

img_gui2.jpg

bg_sig_new.png

hr_sig_new.png

img_sig.png