Access naviehime.com. 愛媛県の地域情報サイト - 愛媛県の事業者情報を無料で掲載【なび愛媛】

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

45/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

74/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value4,310 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value21.8 s

1/100

10%

naviehime.com

405 ms

jquery.min.js

375 ms

fascio.js

334 ms

normalize.min.css

338 ms

main.css

354 ms

Our browser made a total of 134 requests to load all elements on the main page. We found that 31% of them (42 requests) were addressed to the original Naviehime.com, 10% (13 requests) were made to Apis.google.com and 9% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Naviehime.com.

Content Size

821.9 kB

After Optimization

379.9 kB

In fact, the total size of Naviehime.com main page is 821.9 kB. 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. Javascripts take 342.9 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 177.8 kB

Original 245.8 kB
After minification 240.6 kB
After compression 68.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. 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 177.8 kB or 72% of the original size.

Image Optimization

-1%

Potential reduce by 2.5 kB

Original 179.0 kB
After minification 176.5 kB

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. Naviehime images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 215.3 kB

Original 342.9 kB
After minification 342.8 kB
After compression 127.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 215.3 kB or 63% of the original size.

CSS Optimization

-86%

Potential reduce by 46.4 kB

Original 54.2 kB
After minification 43.4 kB
After compression 7.8 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. Naviehime.com needs all CSS files to be minified and compressed as it can save up to 46.4 kB or 86% of the original size.

Requests Now

129

After Optimization

The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Naviehime. 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 5 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

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

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

High

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

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

High

Links are not crawlable

High

robots.txt is not valid

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 Naviehime.com 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 Naviehime.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

naviehime.com

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

naviehime.com

jquery.min.js

fascio.js

normalize.min.css

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

naviehime.com

jquery.min.js

fascio.js

normalize.min.css

main.css

38.js

feed2js.php

jquery.min.js

main.js

gpt.js

navitokuselect.gif

naviehime150x50.gif

yajirusi.gif

new01-002.gif

ico_crown2_2.gif

ico_crown2_3.gif

ico_crown2_4.gif

ico_rank2b_4.gif

ico_rank2b_5.gif

ico_rank2b_6.gif

ico_rank2b_7.gif

ico_rank2b_8.gif

ico_rank2b_9.gif

ico_rank2b_10.gif

qrcode_s_ehime.gif

qrcode_ehime_m.gif

netfloydlogo.png

all.js

famfamfam_icon-information.png

vline.png

glyphish_icon-magnify.png

plugin-38.gif

pubads_impl_82.js

famfamfam_icon-vcard.png

famfamfam_icon-page_white_edit.png

ads

container.html

famfamfam_icon-heart.png

yusuke_kamiyamane_icon-store.png

icon-kurashi.png

icon-kaimono.png

icon-asobu.png

icon-sumai.png