Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

romance-library.jp

ロマンスライブラリトップ | SBCr電子書籍ストア

Page Load Speed

16.5 sec in total

First Response

513 ms

Resources Loaded

14.1 sec

Page Rendered

2 sec

romance-library.jp screenshot

About Website

Click here to check amazing Romance Library content for Mexico. Otherwise, check out these important facts you probably never knew about romance-library.jp

SBクリエイティブ発行のビジネス・実用書からIT関連、ライトノベル、ハーレクインコミックまで多彩なジャンルを取り揃えた直営ECサイト

Visit romance-library.jp

Key Findings

We analyzed Romance-library.jp page load time and found that the first response time was 513 ms and then it took 16 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

romance-library.jp performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value15.5 s

0/100

10%

TBT (Total Blocking Time)

Value880 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value1.422

0/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

romance-library.jp

513 ms

www.romance-library.jp

1313 ms

import.css

561 ms

jquery-ui.css

37 ms

jquery-3.7.1.min.js

39 ms

Our browser made a total of 345 requests to load all elements on the main page. We found that 94% of them (323 requests) were addressed to the original Romance-library.jp, 1% (4 requests) were made to Code.jquery.com and 1% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Romance-library.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (12%)

Content Size

9.7 MB

After Optimization

8.6 MB

In fact, the total size of Romance-library.jp main page is 9.7 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 8.9 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 563.8 kB

  • Original 610.6 kB
  • After minification 498.8 kB
  • After compression 46.8 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 111.8 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 563.8 kB or 92% of the original size.

Image Optimization

-6%

Potential reduce by 522.7 kB

  • Original 8.9 MB
  • After minification 8.4 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. Romance Library images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 13.8 kB

  • Original 114.8 kB
  • After minification 113.3 kB
  • After compression 101.0 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 13.8 kB or 12% of the original size.

CSS Optimization

-26%

Potential reduce by 21.2 kB

  • Original 79.9 kB
  • After minification 76.2 kB
  • After compression 58.7 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. Romance-library.jp needs all CSS files to be minified and compressed as it can save up to 21.2 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 184 (54%)

Requests Now

343

After Optimization

159

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

Accessibility Review

romance-library.jp accessibility score

74

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.

High

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

romance-library.jp 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

romance-library.jp SEO score

73

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

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 doesn't use 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 Romance-library.jp 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 Romance-library.jp 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 Romance Library. 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: