Tools & Wizards About Us
inopedia.tokyo screenshot

Report Summary

  • 89

    Performance

    Renders faster than
    90% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

inopedia.tokyo

伊能忠敬ｅ史料館(InoPedia.tokyo)

Page Load Speed

4.4 sec in total

First Response

529 ms

Resources Loaded

3.7 sec

Page Rendered

195 ms

inopedia.tokyo screenshot

About Website

Visit inopedia.tokyo now to see the best up-to-date Ino Pedia content for Japan and also check out these interesting facts you probably never knew about inopedia.tokyo

伊能忠敬と伊能図の大事典 イノペディア InoPedia ｅ史料館

Visit inopedia.tokyo

Key Findings

We analyzed Inopedia.tokyo page load time and found that the first response time was 529 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

inopedia.tokyo performance score

89

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

87/100

10%

LCP (Largest Contentful Paint)

Value1.9 s

98/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.213

58/100

15%

TTI (Time to Interactive)

Value1.9 s

100/100

10%

Network Requests Diagram

inopedia.tokyo

529 ms

inopedia.tokyo

719 ms

style.css

508 ms

style.css

510 ms

device.css

513 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 91% of them (21 requests) were addressed to the original Inopedia.tokyo, 9% (2 requests) were made to Seal.fujissl.jp. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Inopedia.tokyo.

Page Optimization Overview & Recommendations

Page size can be reduced by 40.9 kB (11%)

Content Size

375.3 kB

After Optimization

334.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inopedia.tokyo main page is 375.3 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. 20% of websites need less resources to load. Images take 346.5 kB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 8.8 kB

  • Original 13.7 kB
  • After minification 11.6 kB
  • After compression 4.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 2.1 kB, which is 15% 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 8.8 kB or 64% of the original size.

Image Optimization

-6%

Potential reduce by 20.4 kB

  • Original 346.5 kB
  • After minification 326.1 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. Ino Pedia images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 83 B

  • Original 230 B
  • After minification 178 B
  • After compression 147 B

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 83 B or 36% of the original size.

CSS Optimization

-78%

Potential reduce by 11.6 kB

  • Original 14.8 kB
  • After minification 10.2 kB
  • After compression 3.2 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. Inopedia.tokyo needs all CSS files to be minified and compressed as it can save up to 11.6 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (14%)

Requests Now

21

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

inopedia.tokyo

inopedia.tokyo

529 ms

inopedia.tokyo

inopedia.tokyo

719 ms

style.css

style.css

508 ms

style.css

style.css

510 ms

device.css

device.css

513 ms

sim2ruby.css

sim2ruby.css

511 ms

winOpen.js

winOpen.js

569 ms

getSeal.do

getSeal.do

907 ms

headbg.jpg

headbg.jpg

514 ms

head.png

head.png

684 ms

topPhotoBl.jpg

topPhotoBl.jpg

696 ms

starDB.png

starDB.png

929 ms

inoDeGo.png

inoDeGo.png

559 ms

s240401110822.jpg

s240401110822.jpg

765 ms

s240206123139.jpg

s240206123139.jpg

1733 ms

s231231181210.jpg

s231231181210.jpg

1513 ms

s190617194814.JPG

s190617194814.JPG

1382 ms

loginBtn.png

loginBtn.png

1203 ms

cyukei2_48.png

cyukei2_48.png

1324 ms

icon01.png

icon01.png

1486 ms

icon.png

icon.png

1724 ms

youtubelogo.png

youtubelogo.png

1883 ms

buildSign.do

buildSign.do

162 ms

Accessibility Review

inopedia.tokyo accessibility score

65

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

inopedia.tokyo best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

inopedia.tokyo SEO score

92

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

Image elements do not have [alt] attributes

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

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 Inopedia.tokyo 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 Inopedia.tokyo 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

inopedia.tokyo

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