Tools & Wizards About Us
forkn.jp screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

forkn.jp

forkN - 漫画（電子書籍）の配信サービスが分かる情報サイト

Page Load Speed

15.3 sec in total

First Response

2.4 sec

Resources Loaded

12.6 sec

Page Rendered

304 ms

forkn.jp screenshot

About Website

Click here to check amazing ForkN content for Japan. Otherwise, check out these important facts you probably never knew about forkn.jp

電子書籍で読める漫画（少年・青年マンガ、少女・女性マンガ、TL・BLマンガ）の配信サービスを掲載｜forkN

Visit forkn.jp

Key Findings

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

Performance Metrics

forkn.jp performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

forkn.jp

2377 ms

jquery-ui-1.8.12.custom.css

203 ms

forkn.css

206 ms

jquery.cleditor.css

599 ms

jplayer.blue.monday.css

880 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Forkn.jp, 83% (80 requests) were made to Cdn.forkn.jp and 3% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (9.7 sec) relates to the external source Cdn.forkn.jp.

Page Optimization Overview & Recommendations

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

Content Size

2.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 33.5 kB

  • Original 41.5 kB
  • After minification 34.3 kB
  • After compression 8.0 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 7.2 kB, which is 17% 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 33.5 kB or 81% of the original size.

Image Optimization

-10%

Potential reduce by 130.9 kB

  • Original 1.3 MB
  • After minification 1.1 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. ForkN images are well optimized though.

JavaScript Optimization

-79%

Potential reduce by 793.3 kB

  • Original 1.0 MB
  • After minification 731.5 kB
  • After compression 216.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 793.3 kB or 79% of the original size.

CSS Optimization

-86%

Potential reduce by 177.1 kB

  • Original 205.5 kB
  • After minification 157.7 kB
  • After compression 28.4 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. Forkn.jp needs all CSS files to be minified and compressed as it can save up to 177.1 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

95

After Optimization

68

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

forkn.jp

forkn.jp

2377 ms

jquery-ui-1.8.12.custom.css

jquery-ui-1.8.12.custom.css

203 ms

forkn.css

forkn.css

206 ms

jquery.cleditor.css

jquery.cleditor.css

599 ms

jplayer.blue.monday.css

jplayer.blue.monday.css

880 ms

codemirror.css

codemirror.css

204 ms

header_logo.png

header_logo.png

578 ms

slide_21.jpg

slide_21.jpg

1552 ms

slide_20.jpg

slide_20.jpg

1473 ms

slide_16.jpg

slide_16.jpg

1785 ms

slide_19.jpg

slide_19.jpg

2585 ms

slide_18.jpg

slide_18.jpg

1590 ms

slide_15.jpg

slide_15.jpg

1899 ms

32x32.png

32x32.png

1649 ms

mEImLHUE

mEImLHUE

1706 ms

ZtsPYpGX

ZtsPYpGX

1831 ms

UokmcWyf

UokmcWyf

1900 ms

rmVJUwAz

rmVJUwAz

2008 ms

3Az14dnx

3Az14dnx

2071 ms

MTNyJthv

MTNyJthv

2166 ms

WcNfoZEB

WcNfoZEB

2211 ms

DeLouWEX

DeLouWEX

2272 ms

Xzoh8k5s

Xzoh8k5s

2355 ms

h2vpEcZN

h2vpEcZN

2377 ms

MtchY089

MtchY089

2906 ms

9YcWI8rG

9YcWI8rG

2529 ms

KzMBeGUy

KzMBeGUy

3081 ms

sxq0bSGX

sxq0bSGX

2696 ms

6XHn3NyM

6XHn3NyM

2700 ms

ANXgmZPv

ANXgmZPv

3001 ms

feuiIuFT

feuiIuFT

2772 ms

WlPLv5kH

WlPLv5kH

2870 ms

YcG1Lg5Q

YcG1Lg5Q

2893 ms

H2oHqvNN

H2oHqvNN

4848 ms

4FfJGuBQ

4FfJGuBQ

3177 ms

SOxinWki

SOxinWki

3270 ms

2Ojd1T4F

2Ojd1T4F

3176 ms

sZJa4wTQ

sZJa4wTQ

3327 ms

MrDuoFzO

MrDuoFzO

3319 ms

WKS1ybbV

WKS1ybbV

3495 ms

widgets.js

widgets.js

5 ms

bookmark_button.js

bookmark_button.js

325 ms

swfobject.js

swfobject.js

3271 ms

libs.js

libs.js

9696 ms

button-only.gif

button-only.gif

168 ms

controls.js

controls.js

2876 ms

394 ms

like.php

like.php

96 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

138 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

153 ms

reset.css

reset.css

9 ms

entry-button.css

entry-button.css

9 ms

button-counter.gif

button-counter.gif

5 ms

common.js

common.js

2392 ms

JtgbJjOG

JtgbJjOG

2719 ms

lHMI1OEy

lHMI1OEy

2444 ms

HYWRhjJp

HYWRhjJp

2546 ms

0UKq8OWC

0UKq8OWC

2436 ms

EAsoZhbf

EAsoZhbf

2470 ms

4evLsRQB

4evLsRQB

2647 ms

x8e4PNIH

x8e4PNIH

2611 ms

tzK0Imab

tzK0Imab

2645 ms

l47XZn8b

l47XZn8b

2579 ms

mgRTRY2c

mgRTRY2c

3370 ms

ixZeXig4

ixZeXig4

4251 ms

q6wVf0wv

q6wVf0wv

2648 ms

K5ZS4LtY

K5ZS4LtY

2770 ms

60x.png

60x.png

2836 ms

M2HAZtTv

M2HAZtTv

2982 ms

kUWm9Te2

kUWm9Te2

2974 ms

newmember.png

newmember.png

3009 ms

side_h2_login.png

side_h2_login.png

2847 ms

side_90_twitter.png

side_90_twitter.png

3207 ms

side_90_artist.png

side_90_artist.png

2917 ms

side_200_contest_creation.png

side_200_contest_creation.png

3623 ms

side_90_media.png

side_90_media.png

2875 ms

side_h2_info.png

side_h2_info.png

2995 ms

bg.png

bg.png

3470 ms

container_bg.png

container_bg.png

3013 ms

header_bg.png

header_bg.png

2888 ms

navigation.png

navigation.png

2942 ms

form_radio_on.png

form_radio_on.png

2997 ms

form_radio.png

form_radio.png

2982 ms

search.png

search.png

3131 ms

top_booklist_bg.png

top_booklist_bg.png

4530 ms

star.png

star.png

3124 ms

arrow_brown.png

arrow_brown.png

3041 ms

login.png

login.png

3042 ms

footer_logo.png

footer_logo.png

2967 ms

footer_gotop.png

footer_gotop.png

2805 ms

ga.js

ga.js

68 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

88 ms

arrow_form.png

arrow_form.png

231 ms

__utm.gif

__utm.gif

14 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

16 ms

jot

jot

93 ms

Accessibility Review

forkn.jp accessibility score

79

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

[role]s do not have all required [aria-*] attributes

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

forkn.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

forkn.jp SEO score

83

Search Engine Optimization Advices

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

forkn.jp

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