2.8 sec in total
189 ms
2 sec
613 ms
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.jpWe 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.
estar.jp performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value4.5 s
38/100
25%
Value16.2 s
0/100
10%
Value3,810 ms
1/100
30%
Value0.008
100/100
15%
Value32.2 s
0/100
10%
189 ms
658 ms
117 ms
34 ms
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 size can be reduced by 607.9 kB (23%)
2.6 MB
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.
Potential reduce by 433.2 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.
Potential reduce by 174.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. Estar images are well optimized though.
Potential reduce by 122 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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 11 (13%)
87
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.
estar.jp
189 ms
estar.jp
658 ms
gtm.js
117 ms
gptInit.js
34 ms
native.js
37 ms
aab0ca9d885cb69e4941.js
68 ms
dc0680fb3cc1a7eb807d.js
75 ms
2f1599ca9654d48dae9c.js
76 ms
f0df856ba88661b24154.js
247 ms
218f8190527a0557922e.js
259 ms
8b45d1ef6ef17b849256.js
273 ms
compass.js
962 ms
for_media.png
366 ms
uwt.js
292 ms
to_extar_ex.png
1082 ms
for_monokaki.png
662 ms
to_estar_popular.png
740 ms
estar_popular.png
388 ms
main.png
253 ms
5_minutes_26.png
255 ms
c3ddf78.png
198 ms
default_user.png
251 ms
title750.png
384 ms
pixta_18621186_1.png
383 ms
06b4e7e3-b25d-4164-8e35-8134d2ce4750.jpg
260 ms
pixta_19312227_1.png
384 ms
8772551b-32fe-4a09-8b85-b5f2e76b739e.jpg
260 ms
b9c60856-6ce1-452d-acf6-982d7759a4ac.jpg
258 ms
9177c772-0595-4656-a2be-16611fd787d4.jpeg
263 ms
629dd0f5-49d9-4164-b92f-3405274c77d0.png
265 ms
e51418d2-d676-4338-8489-c540182a3d8c.jpg
261 ms
fa74b823-c9c6-42c4-897f-deaec92225cc.jpeg
265 ms
996e9015-1b3c-4606-9938-93101793560d.jpeg
267 ms
b5b6abc6-d43c-449a-9234-43bd8c545cb1.jpg
267 ms
e27e7054-2e22-4ee5-bde5-8b5cf06fccb5.jpg
270 ms
pixta_15950190_1.png
455 ms
d0940ab5-2544-4132-9576-461f8a277cd5.jpg
268 ms
default_cover.png
271 ms
a62e38bd-3ece-4348-88eb-293ba0c69935.jpg
272 ms
2f32f9f6-b2d2-460c-8307-1d0a3e69620a.jpeg
284 ms
ffd15d67-0c53-4856-89b0-c36a787a4e0d.jpg
283 ms
dot_02.png
455 ms
0468a2ad-a18a-4120-a56a-8c906b2accd2.jpg
285 ms
tDZERCUT_10.png
457 ms
488435535.jpg
385 ms
4f13fda7-f660-4313-98ef-68787e842b7b.jpeg
386 ms
972c757f-30e2-471c-baed-d93df368eae4.jpg
386 ms
edc88304-1084-4be1-abef-6cd4cf1988f5.jpg
421 ms
485442282.jpg
386 ms
58d55b09-936d-4d56-834e-8dd2fae2ae59.jpg
376 ms
f0d8379d-0614-4438-9fc8-39cecf21e7f8.jpg
378 ms
ytag.js
716 ms
28163774-deb6-4ecd-a24c-3d537b594edc.jpg
197 ms
717a59d4-b28f-4396-8c2e-1357a067408b.jpeg
217 ms
232778f.ttf
188 ms
pixta_15149641_1.png
315 ms
eb8632ea-6165-469c-8fb9-3252825d93e8.png
174 ms
337b81d5-b140-4b47-adfa-8284ee90b981.jpg
174 ms
baf06882-978c-4b56-a536-112539639137.png
176 ms
8ea98814-04c8-4ef5-81a9-9ae55a6b3189.jpg
169 ms
eb0f8e81-1855-478c-9016-642937a06327.png
170 ms
pixta_20397909_1.png
313 ms
b6df08c4-07bc-4310-8643-b75467c97af5.png
169 ms
4c52da3e-497e-4e93-aa7f-01c063f09de1.JPG
168 ms
13ede96c-8f87-4f8a-96f6-5512a6f75703.jpeg
167 ms
93b115a6-c2c7-402a-b44c-72c196e4806c.png
168 ms
tDZERCUT_08.png
306 ms
ugc_01.png
322 ms
941dd4d3-c6d7-47ad-b53d-5fb28390a88a.jpg
188 ms
8d30e6a0-9cc1-4eb8-9c74-6176d1e6160c.png
186 ms
5984ab18-7dcd-43e5-b946-19a58237825e.jpg
187 ms
dbdf0d4b-0eb8-4775-89c7-8644612b0bd6.png
176 ms
489888292.jpg
174 ms
tDZERCUT_06.png
313 ms
pixta_18402936_1.png
326 ms
adsct
126 ms
adsct
124 ms
e73f1b69-2ae4-472e-ac05-caffa70bbcef.png
179 ms
a79bd770-5e68-4e2c-8da9-809a1c147855.jpeg
180 ms
55db26cd-2aac-44ce-87ee-6898567bf216.png
183 ms
tagcategory_1.png
346 ms
recommend_estar_ex_with_ticket.png
190 ms
button.png
187 ms
info_social_straight.png
190 ms
button_follow.png
191 ms
button_add_friend.png
196 ms
info_app.png
191 ms
app_store.png
171 ms
google_play_badge.png
172 ms
to_comic.png
169 ms
estar.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
estar.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
estar.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
JA
JA
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.
estar.jp
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: