Tools & Wizards About Us
ikiya.jp screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

ikiya.jp

粋屋-日本の伝統文様と伝統色

Page Load Speed

23.1 sec in total

First Response

1 sec

Resources Loaded

21.5 sec

Page Rendered

524 ms

ikiya.jp screenshot

About Website

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

ウェブ・グラフィック・名刺デザインなどの背景・壁紙素材として使える日本の伝統文様・和柄の無料画像・EPSファイルの掲載、日本の伝統色のDTP用RGB・CYMK数値と色見本・配色、重ね(襲)の色目を紹介

Visit ikiya.jp

Key Findings

We analyzed Ikiya.jp page load time and found that the first response time was 1 sec and then it took 22.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

ikiya.jp performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.3 s

39/100

10%

Network Requests Diagram

ikiya.jp

1013 ms

import.css

342 ms

ajax.js

343 ms

prototype.js

1025 ms

effects.js

685 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 79% of them (48 requests) were addressed to the original Ikiya.jp, 3% (2 requests) were made to Pagead2.googlesyndication.com and 3% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source Assoc-amazon.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 232.6 kB (27%)

Content Size

858.0 kB

After Optimization

625.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ikiya.jp main page is 858.0 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. 45% of websites need less resources to load. Images take 500.3 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 35.5 kB

  • Original 44.9 kB
  • After minification 32.5 kB
  • After compression 9.4 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 12.4 kB, which is 28% 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 35.5 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 27.2 kB

  • Original 500.3 kB
  • After minification 473.1 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. Ikiya images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 150.3 kB

  • Original 288.1 kB
  • After minification 240.2 kB
  • After compression 137.8 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 150.3 kB or 52% of the original size.

CSS Optimization

-79%

Potential reduce by 19.6 kB

  • Original 24.7 kB
  • After minification 21.2 kB
  • After compression 5.1 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. Ikiya.jp needs all CSS files to be minified and compressed as it can save up to 19.6 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (44%)

Requests Now

55

After Optimization

31

  • Images
  • JavaScript
  • CSS

The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ikiya. 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 from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ikiya.jp

ikiya.jp

1013 ms

import.css

import.css

342 ms

ajax.js

ajax.js

343 ms

prototype.js

prototype.js

1025 ms

effects.js

effects.js

685 ms

index.js

index.js

351 ms

ikiya.js

ikiya.js

510 ms

adsbygoogle.js

adsbygoogle.js

106 ms

google_service.js

google_service.js

19 ms

js

js

70 ms

show_ads.js

show_ads.js

171 ms

page_style.css

page_style.css

172 ms

class_style.css

class_style.css

182 ms

menu_list.css

menu_list.css

185 ms

ukiyoe.css

ukiyoe.css

339 ms

brand

brand

6 ms

astrack.js

astrack.js

337 ms

brandjs.js

brandjs.js

18 ms

ir

ir

19830 ms

main_back.gif

main_back.gif

200 ms

content_sidebar.gif

content_sidebar.gif

200 ms

header.gif

header.gif

341 ms

header_bottom.gif

header_bottom.gif

200 ms

ichimatu_ume_sakura02.gif

ichimatu_ume_sakura02.gif

199 ms

nami01_1.gif

nami01_1.gif

197 ms

nami01_2.gif

nami01_2.gif

702 ms

01koi_001.jpg

01koi_001.jpg

371 ms

02koi_003.jpg

02koi_003.jpg

368 ms

tsuru_026.jpg

tsuru_026.jpg

372 ms

hakuho_001.jpg

hakuho_001.jpg

367 ms

baku_001.jpg

baku_001.jpg

512 ms

tora_001.jpg

tora_001.jpg

537 ms

ukiyoe_001.jpg

ukiyoe_001.jpg

538 ms

kabuki_002.jpg

kabuki_002.jpg

546 ms

nyorai_003.jpg

nyorai_003.jpg

546 ms

CHIYO3.jpg

CHIYO3.jpg

851 ms

CHIYO4.jpg

CHIYO4.jpg

879 ms

CHIYO5.jpg

CHIYO5.jpg

709 ms

CHIYO6.jpg

CHIYO6.jpg

895 ms

CHIYO7.jpg

CHIYO7.jpg

1070 ms

CHIYO8.jpg

CHIYO8.jpg

1040 ms

pt01.gif

pt01.gif

881 ms

pt02.gif

pt02.gif

1022 ms

pt03.gif

pt03.gif

1050 ms

pt04.gif

pt04.gif

1052 ms

pt05.gif

pt05.gif

1070 ms

pt06.gif

pt06.gif

1193 ms

pt07.gif

pt07.gif

1210 ms

wanogakkou_tokuten.gif

wanogakkou_tokuten.gif

1222 ms

ir

ir

19824 ms

topic_back.gif

topic_back.gif

1131 ms

cm

cm

31 ms

cm

cm

30 ms

main_linkmenu.gif

main_linkmenu.gif

1078 ms

monyou_menu_list.gif

monyou_menu_list.gif

1255 ms

color_menu_list.gif

color_menu_list.gif

1197 ms

kasane_menu_list.gif

kasane_menu_list.gif

1212 ms

branding.png

branding.png

21 ms

footer_back.gif

footer_back.gif

1190 ms

ga.js

ga.js

6 ms

__utm.gif

__utm.gif

11 ms

Accessibility Review

ikiya.jp accessibility score

72

Accessibility Issues

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

Form elements do not have associated labels

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

ikiya.jp best practices score

75

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

SEO Factors

ikiya.jp SEO score

69

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

ikiya.jp

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