Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

inaka-pipe.net

いなかパイプ「いなか」と「とかい」のパイプウェブ

Page Load Speed

16.3 sec in total

First Response

1.6 sec

Resources Loaded

13.8 sec

Page Rendered

857 ms

inaka-pipe.net screenshot

About Website

Visit inaka-pipe.net now to see the best up-to-date Inaka Pipe content for Japan and also check out these interesting facts you probably never knew about inaka-pipe.net

「いなかパイプ」は、田舎から発信する情報サイトです。 田舎暮らしをつづったコラムや、いなかのイベント情報、田舎の求人情報、また体験プログラムや、インターンシップの紹介も行っています。

Visit inaka-pipe.net

Key Findings

We analyzed Inaka-pipe.net page load time and found that the first response time was 1.6 sec and then it took 14.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

inaka-pipe.net performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value430 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

inaka-pipe.net

1575 ms

colorbox.css

497 ms

wpp.css

332 ms

styles.css

333 ms

jquery.js

1234 ms

Our browser made a total of 211 requests to load all elements on the main page. We found that 92% of them (195 requests) were addressed to the original Inaka-pipe.net, 2% (5 requests) were made to S7.addthis.com and 1% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Inaka-pipe.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 855.9 kB (37%)

Content Size

2.3 MB

After Optimization

1.5 MB

In fact, the total size of Inaka-pipe.net main page is 2.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. 60% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 200.0 kB

  • Original 255.6 kB
  • After minification 251.1 kB
  • After compression 55.6 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 200.0 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 45.7 kB

  • Original 1.2 MB
  • After minification 1.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. Inaka Pipe images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 569.7 kB

  • Original 867.0 kB
  • After minification 864.4 kB
  • After compression 297.3 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 569.7 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 40.5 kB

  • Original 48.8 kB
  • After minification 37.5 kB
  • After compression 8.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. Inaka-pipe.net needs all CSS files to be minified and compressed as it can save up to 40.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 83 (40%)

Requests Now

210

After Optimization

127

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

Accessibility Review

inaka-pipe.net accessibility score

81

Accessibility Issues

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

High

<object> elements do not have alternate text

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

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

Best Practices

inaka-pipe.net best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

inaka-pipe.net SEO score

82

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    JA

  • Encoding

    UTF-8

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