Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

300books.net

300books|年間300冊くらいしか読書しない人のブログ。

Page Load Speed

6.4 sec in total

First Response

1.7 sec

Resources Loaded

4.1 sec

Page Rendered

644 ms

300books.net screenshot

About Website

Welcome to 300books.net homepage info - get ready to check 300 Books best content for Japan right away, or after learning these important things about 300books.net

Visit 300books.net

Key Findings

We analyzed 300books.net page load time and found that the first response time was 1.7 sec and then it took 4.8 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

300books.net performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value1,490 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

300books.net

1656 ms

normalize.css

514 ms

style.css

354 ms

font-awesome.css

5 ms

styles.css

369 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 61% of them (44 requests) were addressed to the original 300books.net, 7% (5 requests) were made to Pagead2.googlesyndication.com and 7% (5 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Box.c.yimg.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 234.9 kB (32%)

Content Size

738.8 kB

After Optimization

503.8 kB

In fact, the total size of 300books.net main page is 738.8 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. 50% of websites need less resources to load. Images take 433.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 50.9 kB

  • Original 61.5 kB
  • After minification 56.9 kB
  • After compression 10.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 50.9 kB or 83% of the original size.

Image Optimization

-12%

Potential reduce by 52.8 kB

  • Original 433.3 kB
  • After minification 380.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. Obviously, 300 Books needs image optimization as it can save up to 52.8 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-42%

Potential reduce by 74.1 kB

  • Original 175.7 kB
  • After minification 169.1 kB
  • After compression 101.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 74.1 kB or 42% of the original size.

CSS Optimization

-84%

Potential reduce by 57.1 kB

  • Original 68.2 kB
  • After minification 45.7 kB
  • After compression 11.1 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. 300books.net needs all CSS files to be minified and compressed as it can save up to 57.1 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

70

After Optimization

42

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

Accessibility Review

300books.net accessibility score

70

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-*] attributes do not match their roles

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

300books.net 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

300books.net SEO score

83

Search Engine Optimization Advices

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

    N/A

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 300books.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that 300books.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 300 Books. 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: