Tools & Wizards About Us
jikasei.me screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

jikasei.me

自家製フォント工房

Page Load Speed

4 sec in total

First Response

550 ms

Resources Loaded

3.3 sec

Page Rendered

119 ms

jikasei.me screenshot

About Website

Visit jikasei.me now to see the best up-to-date Jikasei content for Japan and also check out these interesting facts you probably never knew about jikasei.me

M+ OUTLINE FONTS, 源ノ角ゴシックをベースとした、商用利用にもご使用いただけるフリーフォント「自家製 Rounded M+」「源真ゴシック」「源柔ゴシック」「Mgen+」「Rounded Mgen+」を頒布しています。

Visit jikasei.me

Key Findings

We analyzed Jikasei.me page load time and found that the first response time was 550 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

jikasei.me performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value17.1 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value3,090 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

jikasei.me

550 ms

style.css

178 ms

jquery.js

504 ms

rs_common.js

332 ms

rs_init.js

332 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 15% of them (15 requests) were addressed to the original Jikasei.me, 20% (20 requests) were made to Platform.twitter.com and 9% (9 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (628 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 70.4 kB (8%)

Content Size

882.8 kB

After Optimization

812.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jikasei.me main page is 882.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 665.4 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 36.7 kB

  • Original 48.6 kB
  • After minification 48.0 kB
  • After compression 11.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 36.7 kB or 76% of the original size.

Image Optimization

-19%

Potential reduce by 31.4 kB

  • Original 165.7 kB
  • After minification 134.4 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, Jikasei needs image optimization as it can save up to 31.4 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 1.8 kB

  • Original 665.4 kB
  • After minification 665.4 kB
  • After compression 663.7 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.

CSS Optimization

-17%

Potential reduce by 511 B

  • Original 3.0 kB
  • After minification 3.0 kB
  • After compression 2.5 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. Jikasei.me needs all CSS files to be minified and compressed as it can save up to 511 B or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (68%)

Requests Now

92

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jikasei.me

jikasei.me

550 ms

style.css

style.css

178 ms

jquery.js

jquery.js

504 ms

rs_common.js

rs_common.js

332 ms

rs_init.js

rs_init.js

332 ms

rs_crossfade.js

rs_crossfade.js

333 ms

rs_thumbnail.js

rs_thumbnail.js

341 ms

adsbygoogle.js

adsbygoogle.js

146 ms

button-only.gif

button-only.gif

69 ms

title.png

title.png

216 ms

show_ads_impl.js

show_ads_impl.js

438 ms

button-only.gif

button-only.gif

23 ms

widgets.js

widgets.js

12 ms

ga.js

ga.js

11 ms

plusone.js

plusone.js

54 ms

bookmark_button_wo_al.js

bookmark_button_wo_al.js

9 ms

btn.js

btn.js

70 ms

analytics.js

analytics.js

39 ms

bookmark_button_wo_al.js

bookmark_button_wo_al.js

38 ms

all.js

all.js

61 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

71 ms

__utm.gif

__utm.gif

31 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

19 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

67 ms

fastbutton

fastbutton

63 ms

button

button

4 ms

all.js

all.js

22 ms

widgetButton.91d9e0cb42c020d8c4b1.css

widgetButton.91d9e0cb42c020d8c4b1.css

75 ms

widgetButton.7edb5a95ac874e928813.js

widgetButton.7edb5a95ac874e928813.js

76 ms

settings

settings

160 ms

postmessageRelay

postmessageRelay

39 ms

3636781319-postmessagerelay.js

3636781319-postmessagerelay.js

25 ms

rpc:shindig_random.js

rpc:shindig_random.js

12 ms

developers.google.com

developers.google.com

309 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

3 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

7 ms

rounded_mplus

rounded_mplus

73 ms

embeds

embeds

102 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

26 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

5 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

2 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

24 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

32 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

46 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

50 ms

_buildManifest.js

_buildManifest.js

58 ms

_ssgManifest.js

_ssgManifest.js

59 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

11 ms

7651.a95a6a76dc7859214377.js

7651.a95a6a76dc7859214377.js

10 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

22 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

22 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

22 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

24 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

21 ms

zrt_lookup.html

zrt_lookup.html

73 ms

ads

ads

628 ms

ads

ads

429 ms

ads

ads

544 ms

reactive_library.js

reactive_library.js

163 ms

load_preloaded_resource.js

load_preloaded_resource.js

42 ms

abg_lite.js

abg_lite.js

45 ms

s

s

25 ms

window_focus.js

window_focus.js

127 ms

qs_click_protection.js

qs_click_protection.js

48 ms

ufs_web_display.js

ufs_web_display.js

39 ms

5f7468413707c3abfd197d65a482477f.js

5f7468413707c3abfd197d65a482477f.js

48 ms

icon.png

icon.png

34 ms

ads

ads

279 ms

css

css

51 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

25 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

62 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

66 ms

activeview

activeview

160 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

47 ms

7f032190f136c4d8e9a385e88120dc8d.js

7f032190f136c4d8e9a385e88120dc8d.js

30 ms

af5cf33f216dd68f5f355584e69bf9d6.js

af5cf33f216dd68f5f355584e69bf9d6.js

34 ms

kicKnkvfK75Ziq-i9jQCXBfdaqJwezh_xrK1nzwiJeU.js

kicKnkvfK75Ziq-i9jQCXBfdaqJwezh_xrK1nzwiJeU.js

114 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

122 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

158 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDXbtY.ttf

166 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf

183 ms

14763004658117789537

14763004658117789537

106 ms

css

css

72 ms

css

css

73 ms

font

font

3 ms

setting.xml

setting.xml

177 ms

sodar

sodar

72 ms

activeview

activeview

61 ms

like.php

like.php

232 ms

sodar2.js

sodar2.js

4 ms

runner.html

runner.html

5 ms

aframe

aframe

23 ms

jikasei.png

jikasei.png

354 ms

slide-roundedmplus.png

slide-roundedmplus.png

330 ms

slide-genshin.png

slide-genshin.png

327 ms

slide-genjyuu.png

slide-genjyuu.png

333 ms

slide-mgenplus.png

slide-mgenplus.png

344 ms

slide-roundedmgenplus.png

slide-roundedmgenplus.png

165 ms

Hi2jWCVayBK.js

Hi2jWCVayBK.js

22 ms

FEppCFCt76d.png

FEppCFCt76d.png

14 ms

Accessibility Review

jikasei.me accessibility score

78

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

jikasei.me best practices score

58

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

jikasei.me SEO score

67

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jikasei.me 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 Jikasei.me main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

jikasei.me

Open Graph description is not detected on the main page of Jikasei. 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: