Tools & Wizards About Us
rikiy.jp screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

rikiy.jp

Studio Rikiy

Page Load Speed

3.9 sec in total

First Response

763 ms

Resources Loaded

3 sec

Page Rendered

138 ms

rikiy.jp screenshot

About Website

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

Webデザイナー兼漫画家志望、RikiyのHP(ホームページ)です。オリジナルのマンガとイラスト、Webに関する情報の公開をしています。

Visit rikiy.jp

Key Findings

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

Performance Metrics

rikiy.jp performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

87/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value7.8 s

45/100

10%

Network Requests Diagram

rikiy.jp

763 ms

viewer.js

548 ms

function.js

540 ms

import_home.css

361 ms

lpo.js

202 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 47% of them (36 requests) were addressed to the original Rikiy.jp, 12% (9 requests) were made to Plugins.mixi.jp and 12% (9 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Rikiy.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 479.8 kB (52%)

Content Size

917.6 kB

After Optimization

437.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rikiy.jp main page is 917.6 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. 40% of websites need less resources to load. Javascripts take 627.4 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 11.0 kB

  • Original 15.2 kB
  • After minification 15.0 kB
  • After compression 4.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 11.0 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 1.3 kB

  • Original 226.7 kB
  • After minification 225.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. Rikiy images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 428.2 kB

  • Original 627.4 kB
  • After minification 578.3 kB
  • After compression 199.2 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 428.2 kB or 68% of the original size.

CSS Optimization

-81%

Potential reduce by 39.3 kB

  • Original 48.3 kB
  • After minification 37.5 kB
  • After compression 9.0 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. Rikiy.jp needs all CSS files to be minified and compressed as it can save up to 39.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 49 (66%)

Requests Now

74

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rikiy.jp

rikiy.jp

763 ms

viewer.js

viewer.js

548 ms

function.js

function.js

540 ms

import_home.css

import_home.css

361 ms

lpo.js

lpo.js

202 ms

banar.js

banar.js

362 ms

social.js

social.js

377 ms

sitemap.js

sitemap.js

383 ms

gy.js

gy.js

390 ms

news.js

news.js

539 ms

base.css

base.css

186 ms

common.css

common.css

361 ms

style_home.css

style_home.css

187 ms

logo.gif

logo.gif

200 ms

topimg.jpg

topimg.jpg

1047 ms

icn_illust.gif

icn_illust.gif

345 ms

bnr_extia.gif

bnr_extia.gif

556 ms

bnr_cgwp.gif

bnr_cgwp.gif

735 ms

bg_hd.gif

bg_hd.gif

209 ms

bg_hdbar.gif

bg_hdbar.gif

182 ms

icon_search.gif

icon_search.gif

182 ms

bg_sbox.gif

bg_sbox.gif

207 ms

arrow_pulldown.gif

arrow_pulldown.gif

208 ms

bg2_topimg.jpg

bg2_topimg.jpg

364 ms

bg_topimg.jpg

bg_topimg.jpg

902 ms

bg_info.gif

bg_info.gif

389 ms

h2_info.gif

h2_info.gif

391 ms

bg_dot.gif

bg_dot.gif

394 ms

icn_comic.gif

icn_comic.gif

542 ms

icn_report.gif

icn_report.gif

573 ms

icn_comicrikiy.gif

icn_comicrikiy.gif

574 ms

icn_extia.gif

icn_extia.gif

585 ms

icn_cgw.gif

icn_cgw.gif

728 ms

rikiybn01.gif

rikiybn01.gif

756 ms

rikiybn02.gif

rikiybn02.gif

746 ms

widgets.js

widgets.js

128 ms

button-only.gif

button-only.gif

349 ms

bookmark_button.js

bookmark_button.js

703 ms

share

share

328 ms

favorite.pl

favorite.pl

370 ms

icn_pt.gif

icn_pt.gif

607 ms

ga.js

ga.js

29 ms

like.php

like.php

100 ms

__utm.gif

__utm.gif

12 ms

k1rbomb5QdI.css

k1rbomb5QdI.css

173 ms

WKVr13EZyG7.css

WKVr13EZyG7.css

213 ms

LZPfy0u--eK.css

LZPfy0u--eK.css

267 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

372 ms

DFmZn3_ZO2h.js

DFmZn3_ZO2h.js

308 ms

mfqI3d6rUg1.js

mfqI3d6rUg1.js

404 ms

_Qp3v7kqEMi.js

_Qp3v7kqEMi.js

402 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

11 ms

btn_iine_20.png

btn_iine_20.png

368 ms

mixi_check_entry.css

mixi_check_entry.css

12 ms

errorreport.production.js

errorreport.production.js

296 ms

json.js

json.js

298 ms

underscore-string-1.3.3-2.0.0-compress.js

underscore-string-1.3.3-2.0.0-compress.js

301 ms

namespace-brook-compress.js

namespace-brook-compress.js

301 ms

prototype-effects-1.6.1-1.8.3-compress.js

prototype-effects-1.6.1-1.8.3-compress.js

449 ms

mixi.js

mixi.js

309 ms

plugins.js

plugins.js

444 ms

favorite.production.js

favorite.production.js

590 ms

jquery-1.7.1.min-noconflict-compress.js

jquery-1.7.1.min-noconflict-compress.js

743 ms

bnr_extia.gif

bnr_extia.gif

759 ms

Bw8qRoQ9D-v.js

Bw8qRoQ9D-v.js

44 ms

4ylGxU24Rah.js

4ylGxU24Rah.js

129 ms

432 ms

analytics.js

analytics.js

3 ms

comment001.gif

comment001.gif

6 ms

reset.css

reset.css

10 ms

entry-button.css

entry-button.css

12 ms

button-counter.gif

button-counter.gif

5 ms

favorite_button003-.png

favorite_button003-.png

5 ms

comment_content_top001.gif

comment_content_top001.gif

4 ms

loading.gif

loading.gif

186 ms

b-cls.gif

b-cls.gif

182 ms

Accessibility Review

rikiy.jp accessibility score

88

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

Best Practices

rikiy.jp best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

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

Links do not have descriptive text

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

rikiy.jp

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