Tools & Wizards About Us

Report Summary

  • 84

    Performance

    Renders faster than
    88% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

y-history.net

世界史の窓

Page Load Speed

5 sec in total

First Response

681 ms

Resources Loaded

2.8 sec

Page Rendered

1.6 sec

About Website

Visit y-history.net now to see the best up-to-date Y History content for Japan and also check out these interesting facts you probably never knew about y-history.net

世界史学習のためのノートを中心としたページです。

Visit y-history.net

Key Findings

We analyzed Y-history.net page load time and found that the first response time was 681 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

y-history.net performance score

84

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

80/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value150 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.183

66/100

15%

TTI (Time to Interactive)

Value2.7 s

97/100

10%

Network Requests Diagram

y-history.net

681 ms

y-history.net

740 ms

index-css.css

175 ms

note_js.js

350 ms

count.php

253 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that all of those requests were addressed to Y-history.net and no external sources were called. The less responsive or slowest element that took the longest time to load (878 ms) belongs to the original domain Y-history.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 28.4 kB (68%)

Content Size

42.1 kB

After Optimization

13.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Y-history.net main page is 42.1 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. Only 10% of websites need less resources to load. CSS take 22.7 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 5.7 kB

  • Original 8.7 kB
  • After minification 7.1 kB
  • After compression 2.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 1.6 kB, which is 18% 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 5.7 kB or 66% of the original size.

Image Optimization

-32%

Potential reduce by 3.0 kB

  • Original 9.4 kB
  • After minification 6.4 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. Obviously, Y History needs image optimization as it can save up to 3.0 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-75%

Potential reduce by 992 B

  • Original 1.3 kB
  • After minification 977 B
  • After compression 330 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 992 B or 75% of the original size.

CSS Optimization

-83%

Potential reduce by 18.7 kB

  • Original 22.7 kB
  • After minification 15.5 kB
  • After compression 4.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. Y-history.net needs all CSS files to be minified and compressed as it can save up to 18.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (44%)

Requests Now

16

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

y-history.net accessibility score

82

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

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

Best Practices

y-history.net best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

y-history.net SEO score

100

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

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 Y-history.net 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 Y-history.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 Y History. 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: