Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

estar.jp

【エブリスタ】おすすめの携帯・web小説が無料で読める/小説投稿サイト

Page Load Speed

2.8 sec in total

First Response

189 ms

Resources Loaded

2 sec

Page Rendered

613 ms

estar.jp screenshot

About Website

Welcome to estar.jp homepage info - get ready to check Estar best content for Japan right away, or after learning these important things about estar.jp

【エブリスタ】は、おすすめ/人気の恋愛小説・ファンタジー小説・BL小説などを無料で読める小説投稿サイトです。大人の恋・学園・オフィスラブなど、細かなジャンルまで検索できます。エブリスタから誕生した作品も多数!誰にでも小説家デビューのチャンスがあります!

Visit estar.jp

Key Findings

We analyzed Estar.jp page load time and found that the first response time was 189 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

estar.jp performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

38/100

25%

SI (Speed Index)

Value16.2 s

0/100

10%

TBT (Total Blocking Time)

Value3,810 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value32.2 s

0/100

10%

Network Requests Diagram

estar.jp

189 ms

estar.jp

658 ms

gtm.js

117 ms

gptInit.js

34 ms

native.js

37 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 8% of them (7 requests) were addressed to the original Estar.jp, 86% (77 requests) were made to Img.estar.jp and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Estar.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 607.9 kB (23%)

Content Size

2.6 MB

After Optimization

2.0 MB

In fact, the total size of Estar.jp main page is 2.6 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 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 433.2 kB

  • Original 472.1 kB
  • After minification 470.9 kB
  • After compression 38.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 433.2 kB or 92% of the original size.

Image Optimization

-10%

Potential reduce by 174.5 kB

  • Original 1.8 MB
  • After minification 1.7 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. Estar images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 122 B

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

Requests Breakdown

Number of requests can be reduced by 11 (13%)

Requests Now

87

After Optimization

76

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

Accessibility Review

estar.jp accessibility score

93

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

High

Links do not have a discernible name

Best Practices

estar.jp 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

estar.jp SEO score

81

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 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 Estar.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 Estar.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 Estar. 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: