Access takedive.jp. 沖縄テクニカルダイビング TAKEDIVE

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value24.1 s

0/100

10%

TBT (Total Blocking Time)

Value5,560 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value95.4 s

0/100

10%

takedive.jp

512 ms

takedive.jp

715 ms

www.takedive.jp

2019 ms

wp-emoji-release.min.js

686 ms

style.min.css

1194 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 50% of them (55 requests) were addressed to the original Takedive.jp, 11% (12 requests) were made to Img.youtube.com and 7% (8 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (6.6 sec) belongs to the original domain Takedive.jp.

Content Size

3.3 MB

After Optimization

2.7 MB

In fact, the total size of Takedive.jp main page is 3.3 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. 80% 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 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 85.7 kB

Original 102.7 kB
After minification 80.4 kB
After compression 17.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. This page needs HTML code to be minified as it can gain 22.3 kB, which is 22% 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 85.7 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 28.0 kB

Original 2.4 MB
After minification 2.3 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. TAKEDIVE images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 279.0 kB

Original 572.2 kB
After minification 567.9 kB
After compression 293.2 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 279.0 kB or 49% of the original size.

CSS Optimization

-64%

Potential reduce by 159.9 kB

Original 248.9 kB
After minification 226.5 kB
After compression 89.0 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. Takedive.jp needs all CSS files to be minified and compressed as it can save up to 159.9 kB or 64% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

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

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

JA
Encoding

UTF-8

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

takedive.jp

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

沖縄テクニカルダイビング TAKEDIVE

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

takedive.jp

takedive.jp

www.takedive.jp

wp-emoji-release.min.js

style.min.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

takedive.jp

takedive.jp

www.takedive.jp

wp-emoji-release.min.js

style.min.css

classic-themes.min.css

bb497957ba.js

jquery-1.9.1.js

slick.css

slick-theme.css

slick.min.js

style.css

css2

js

unite-gallery.css

skin-right-thumb.css

jquery.min.js

jquery-migrate.min.js

player_api

unitegallery.min.js

ug-theme-video.js

js

wejs

cai6zjg.js

notosansjp.css

Tripadvisor_logomark.svg

logo_w.svg

collage.png

licence-tec.jpg

licence-fullcave.jpg

licence-introcave.jpg

licence-cavern.jpg

licence-green.jpg

GOPR5351-800x600.jpg

GPTempDownload-120-800x450.jpg

%E3%83%97%E3%83%AA%E3%82%BA%E3%83%A0-2%E4%BD%93%E9%A8%93%E3%81%AE%E3%82%B3%E3%83%94%E3%83%BC-800x800.jpg

Decompression-diving.jpg

GOPR5225%E3%81%AE%E3%82%B3%E3%83%94%E3%83%BC.jpg

IMG_9739-e1641618989239-800x800.jpg

GOPR5845-e1641542923874-800x800.jpg

IMG_7338-e1641613316670-800x800.jpg

GOPR5761-e1642317470907-800x800.jpg

GPTempDownload-4-1-800x800.jpg