Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

akioota-navi.jp

あきおおたナビ 安芸太田ナビ 広島県安芸太田町の観光をご案内 一般社団法人地域商社あきおおた

Page Load Speed

18.8 sec in total

First Response

1.4 sec

Resources Loaded

17 sec

Page Rendered

404 ms

akioota-navi.jp screenshot

About Website

Welcome to akioota-navi.jp homepage info - get ready to check Akioota Navi best content for Japan right away, or after learning these important things about akioota-navi.jp

自然環境に恵まれた、広島県安芸太田町の観光スポットやイベント情報を紹介しています。安芸太田ナビ あきおおたナビ 地域商社あきおおた

Visit akioota-navi.jp

Key Findings

We analyzed Akioota-navi.jp page load time and found that the first response time was 1.4 sec and then it took 17.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

akioota-navi.jp performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value1,600 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.202

61/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

akioota-navi.jp

1361 ms

boilerplate.css

183 ms

rayout.css

321 ms

styleswitcher.js

332 ms

respond.min.js

345 ms

Our browser made a total of 151 requests to load all elements on the main page. We found that 34% of them (52 requests) were addressed to the original Akioota-navi.jp, 26% (39 requests) were made to Static.xx.fbcdn.net and 15% (22 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (14.6 sec) belongs to the original domain Akioota-navi.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 691.7 kB (23%)

Content Size

3.1 MB

After Optimization

2.4 MB

In fact, the total size of Akioota-navi.jp main page is 3.1 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. 70% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 26.8 kB

  • Original 34.0 kB
  • After minification 23.7 kB
  • After compression 7.2 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 10.3 kB, which is 30% 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 26.8 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 34.5 kB

  • Original 2.2 MB
  • After minification 2.1 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. Akioota Navi images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 326.3 kB

  • Original 520.1 kB
  • After minification 508.7 kB
  • After compression 193.8 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 326.3 kB or 63% of the original size.

CSS Optimization

-84%

Potential reduce by 304.2 kB

  • Original 361.9 kB
  • After minification 339.1 kB
  • After compression 57.7 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. Akioota-navi.jp needs all CSS files to be minified and compressed as it can save up to 304.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 78 (53%)

Requests Now

147

After Optimization

69

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

Accessibility Review

akioota-navi.jp accessibility score

68

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Names and labels

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.

Impact

Issue

High

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

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

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

Tables and lists

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

Impact

Issue

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.

Best Practices

akioota-navi.jp best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

akioota-navi.jp SEO score

98

Search Engine Optimization Advices

Mobile Friendly

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

Impact

Issue

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 Akioota-navi.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 Akioota-navi.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

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