Tools & Wizards About Us
historivia.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

historivia.com

ひすとりびあ | 歴史の雑学サイト

Page Load Speed

8.1 sec in total

First Response

543 ms

Resources Loaded

7.4 sec

Page Rendered

197 ms

historivia.com screenshot

About Website

Visit historivia.com now to see the best up-to-date Historivia content for Japan and also check out these interesting facts you probably never knew about historivia.com

ひすとりびあでは歴史の雑学的な事柄や知識を紹介しています。これで貴方も歴史博士？

Visit historivia.com

Key Findings

We analyzed Historivia.com page load time and found that the first response time was 543 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

historivia.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value860 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.483

17/100

15%

TTI (Time to Interactive)

Value12.7 s

14/100

10%

Network Requests Diagram

historivia.com

543 ms

historivia.com

1183 ms

wp-emoji-release.min.js

197 ms

style.min.css

393 ms

styles.css

510 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 53% of them (35 requests) were addressed to the original Historivia.com, 20% (13 requests) were made to I0.wp.com and 17% (11 requests) were made to I2.wp.com. The less responsive or slowest element that took the longest time to load (4.4 sec) relates to the external source I1.wp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 201.0 kB (24%)

Content Size

825.2 kB

After Optimization

624.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Historivia.com main page is 825.2 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. 40% of websites need less resources to load. Images take 574.8 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 45.2 kB

  • Original 55.1 kB
  • After minification 52.3 kB
  • After compression 9.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. 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 45.2 kB or 82% of the original size.

Image Optimization

-22%

Potential reduce by 127.5 kB

  • Original 574.8 kB
  • After minification 447.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, Historivia needs image optimization as it can save up to 127.5 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-9%

Potential reduce by 13.3 kB

  • Original 143.1 kB
  • After minification 142.5 kB
  • After compression 129.7 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. This website has mostly compressed JavaScripts.

CSS Optimization

-29%

Potential reduce by 15.0 kB

  • Original 52.2 kB
  • After minification 52.2 kB
  • After compression 37.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. Historivia.com needs all CSS files to be minified and compressed as it can save up to 15.0 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (38%)

Requests Now

63

After Optimization

39

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

historivia.com

historivia.com

543 ms

historivia.com

historivia.com

1183 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

197 ms

style.min.css

style.min.css

393 ms

styles.css

styles.css

510 ms

style.css

style.css

509 ms

jetpack.css

jetpack.css

778 ms

jquery.js

jquery.js

785 ms

jquery-migrate.min.js

jquery-migrate.min.js

586 ms

adsbygoogle.js

adsbygoogle.js

67 ms

style.css

style.css

587 ms

comment-style.css

comment-style.css

678 ms

japanese.css

japanese.css

677 ms

jscript.js

jscript.js

801 ms

scroll.js

scroll.js

802 ms

comment.js

comment.js

855 ms

rollover.js

rollover.js

855 ms

slick.css

slick.css

972 ms

photon.min.js

photon.min.js

974 ms

scripts.js

scripts.js

976 ms

devicepx-jetpack.js

devicepx-jetpack.js

23 ms

wp-embed.min.js

wp-embed.min.js

974 ms

jquery.easing.js

jquery.easing.js

1016 ms

slick.min.js

slick.min.js

1018 ms

e-202432.js

e-202432.js

24 ms

style_pc.css

style_pc.css

368 ms

45dw9sa.jpg

45dw9sa.jpg

186 ms

4604017534_29c7f1aef91.jpg

4604017534_29c7f1aef91.jpg

1344 ms

17e4d79bccd2ce873c7c0feb8fd0c83a_s.jpg

17e4d79bccd2ce873c7c0feb8fd0c83a_s.jpg

197 ms

2039378685_f1975fb0f2.jpg

2039378685_f1975fb0f2.jpg

1411 ms

90672281_e82cefc374.jpg

90672281_e82cefc374.jpg

4446 ms

Toshimichi_Okubo_in_the_Aoyama_Cemetery.jpg

Toshimichi_Okubo_in_the_Aoyama_Cemetery.jpg

192 ms

logo.png

logo.png

603 ms

arrow1.png

arrow1.png

215 ms

icon_rss.png

icon_rss.png

191 ms

icon_twitter.png

icon_twitter.png

189 ms

search_input.gif

search_input.gif

214 ms

search_button.gif

search_button.gif

215 ms

headline1.gif

headline1.gif

360 ms

footer-image.png

footer-image.png

697 ms

6122294263_8f6e2a7414.jpg

6122294263_8f6e2a7414.jpg

201 ms

4604017534_29c7f1aef91.jpg

4604017534_29c7f1aef91.jpg

1695 ms

6122294263_8f6e2a7414.jpg

6122294263_8f6e2a7414.jpg

200 ms

Eiraku-Tsuho.jpg

Eiraku-Tsuho.jpg

183 ms

16473903670_5e3dcc2a66.jpg

16473903670_5e3dcc2a66.jpg

209 ms

3289102754_966517d01d.jpg

3289102754_966517d01d.jpg

198 ms

2009C7AF7B7EE2020C6FC24-27C6FCBBB3B8FDCEB9B9D4C2BE20076.jpg

2009C7AF7B7EE2020C6FC24-27C6FCBBB3B8FDCEB9B9D4C2BE20076.jpg

1167 ms

4981682317_5caf584cf6.jpg

4981682317_5caf584cf6.jpg

3250 ms

8341941678_ca6ea6cd27.jpg

8341941678_ca6ea6cd27.jpg

220 ms

Toshiyoshi_Kawaji_thumb1.jpg

Toshiyoshi_Kawaji_thumb1.jpg

218 ms

4604017534_29c7f1aef9.jpg

4604017534_29c7f1aef9.jpg

273 ms

45dw9sa.jpg

45dw9sa.jpg

178 ms

4604017534_29c7f1aef9.jpg

4604017534_29c7f1aef9.jpg

175 ms

c6a6e002e4b13df0eadaf1ecab988bd0_s.jpg

c6a6e002e4b13df0eadaf1ecab988bd0_s.jpg

193 ms

9b5fdb1a5788d83bbeeb11ca76231ac9_s.jpg

9b5fdb1a5788d83bbeeb11ca76231ac9_s.jpg

192 ms

dbd0240487d758c56c5af62f57929883_s.jpg

dbd0240487d758c56c5af62f57929883_s.jpg

1043 ms

95529c1aa85621b971c75aaeaef9850d_s.jpg

95529c1aa85621b971c75aaeaef9850d_s.jpg

1218 ms

16152975963_bfef8e37a1.jpg

16152975963_bfef8e37a1.jpg

3957 ms

4479733801_4f307abec2.jpg

4479733801_4f307abec2.jpg

2129 ms

9620628505_470d0f590f.jpg

9620628505_470d0f590f.jpg

1984 ms

3382017286_603883c1b6.jpg

3382017286_603883c1b6.jpg

289 ms

490857315_360fc7910d.jpg

490857315_360fc7910d.jpg

322 ms

return_top.png

return_top.png

308 ms

design_plus.woff

design_plus.woff

304 ms

style_sp.css

style_sp.css

197 ms

footer-bar.css

footer-bar.css

197 ms

Accessibility Review

historivia.com accessibility score

86

Accessibility Issues

ARIA

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.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

historivia.com best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

historivia.com 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 Historivia.com 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 Historivia.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

historivia.com

Open Graph data is detected on the main page of Historivia. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: