Tools & Wizards About Us
ikiya.jp screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

ikiya.jp

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

Page Load Speed

4.9 sec in total

First Response

1.1 sec

Resources Loaded

3.1 sec

Page Rendered

732 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.1 sec and then it took 3.8 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

ikiya.jp performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

46/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value1,950 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.3 s

3/100

10%

Network Requests Diagram

ikiya.jp

1130 ms

import.css

296 ms

ajax.js

300 ms

prototype.js

1098 ms

effects.js

837 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 47% of them (48 requests) were addressed to the original Ikiya.jp, 8% (8 requests) were made to Googleads.g.doubleclick.net and 5% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Ikiya.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 397.9 kB (41%)

Content Size

960.8 kB

After Optimization

563.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 42.0 kB

  • Original 52.2 kB
  • After minification 39.8 kB
  • After compression 10.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. This page needs HTML code to be minified as it can gain 12.4 kB, which is 24% 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 42.0 kB or 80% of the original size.

Image Optimization

-18%

Potential reduce by 94.8 kB

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

JavaScript Optimization

-70%

Potential reduce by 241.4 kB

  • Original 344.3 kB
  • After minification 296.2 kB
  • After compression 102.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 241.4 kB or 70% 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 44 (45%)

Requests Now

98

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 98 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 22 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

1130 ms

import.css

import.css

296 ms

ajax.js

ajax.js

300 ms

prototype.js

prototype.js

1098 ms

effects.js

effects.js

837 ms

index.js

index.js

341 ms

ikiya.js

ikiya.js

728 ms

google_service.js

google_service.js

18 ms

show_ads.js

show_ads.js

5 ms

page_style.css

page_style.css

297 ms

class_style.css

class_style.css

388 ms

menu_list.css

menu_list.css

442 ms

ukiyoe.css

ukiyoe.css

443 ms

brand

brand

35 ms

astrack.js

astrack.js

304 ms

brand

brand

64 ms

google_ads.js

google_ads.js

20 ms

main_back.gif

main_back.gif

243 ms

ir

ir

158 ms

content_sidebar.gif

content_sidebar.gif

191 ms

header.gif

header.gif

337 ms

header_bottom.gif

header_bottom.gif

191 ms

ichimatu_ume_sakura02.gif

ichimatu_ume_sakura02.gif

295 ms

nami01_1.gif

nami01_1.gif

154 ms

nami01_2.gif

nami01_2.gif

637 ms

01koi_001.jpg

01koi_001.jpg

358 ms

02koi_003.jpg

02koi_003.jpg

337 ms

tsuru_026.jpg

tsuru_026.jpg

396 ms

hakuho_001.jpg

hakuho_001.jpg

441 ms

baku_001.jpg

baku_001.jpg

510 ms

tora_001.jpg

tora_001.jpg

509 ms

ukiyoe_001.jpg

ukiyoe_001.jpg

528 ms

kabuki_002.jpg

kabuki_002.jpg

570 ms

nyorai_003.jpg

nyorai_003.jpg

640 ms

CHIYO3.jpg

CHIYO3.jpg

661 ms

CHIYO4.jpg

CHIYO4.jpg

847 ms

CHIYO5.jpg

CHIYO5.jpg

873 ms

CHIYO6.jpg

CHIYO6.jpg

937 ms

CHIYO7.jpg

CHIYO7.jpg

928 ms

CHIYO8.jpg

CHIYO8.jpg

925 ms

pt01.gif

pt01.gif

816 ms

pt02.gif

pt02.gif

973 ms

pt03.gif

pt03.gif

1014 ms

pt04.gif

pt04.gif

1043 ms

pt05.gif

pt05.gif

1070 ms

pt06.gif

pt06.gif

1074 ms

pt07.gif

pt07.gif

1122 ms

wanogakkou_tokuten.gif

wanogakkou_tokuten.gif

1127 ms

ir

ir

243 ms

zrt_lookup.html

zrt_lookup.html

27 ms

show_ads_impl.js

show_ads_impl.js

45 ms

ads

ads

243 ms

topic_back.gif

topic_back.gif

1048 ms

ads

ads

220 ms

osd.js

osd.js

37 ms

ads

ads

172 ms

ads

ads

242 ms

ads

ads

217 ms

cm

cm

278 ms

cm

cm

249 ms

main_linkmenu.gif

main_linkmenu.gif

983 ms

monyou_menu_list.gif

monyou_menu_list.gif

984 ms

color_menu_list.gif

color_menu_list.gif

988 ms

kasane_menu_list.gif

kasane_menu_list.gif

1077 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

85 ms

ads

ads

188 ms

footer_back.gif

footer_back.gif

1018 ms

ga.js

ga.js

30 ms

__utm.gif

__utm.gif

11 ms

abg.js

abg.js

33 ms

116 ms

adj

adj

69 ms

beacon

beacon

52 ms

51Y6+6N9dYL._SL100_.jpg

51Y6+6N9dYL._SL100_.jpg

14 ms

181 ms

buy-from-tan.gif

buy-from-tan.gif

7 ms

5199Bd8gMOL._SL100_.jpg

5199Bd8gMOL._SL100_.jpg

27 ms

236 ms

66 ms

activityi;src=4236808;type=invmedia;cat=qk1cfvwl;ord=-1359774198

activityi;src=4236808;type=invmedia;cat=qk1cfvwl;ord=-1359774198

219 ms

activityi;src=4236808;type=invmedia;cat=4ztf2oue;ord=-1359774198

activityi;src=4236808;type=invmedia;cat=4ztf2oue;ord=-1359774198

75 ms

activityi;src=4236808;type=invmedia;cat=ijhardnr;ord=-1359774198

activityi;src=4236808;type=invmedia;cat=ijhardnr;ord=-1359774198

151 ms

activityi;src=4236808;type=invmedia;cat=aoyjbkr6;ord=-1359774198

activityi;src=4236808;type=invmedia;cat=aoyjbkr6;ord=-1359774198

153 ms

0

0

155 ms

pixel

pixel

40 ms

lidar.js

lidar.js

58 ms

sbhK2lTE.js

sbhK2lTE.js

18 ms

cTrvNaRi.html

cTrvNaRi.html

14 ms

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

30 ms

pixel

pixel

111 ms

pixel

pixel

115 ms

NSWW00532999.jpg

NSWW00532999.jpg

178 ms

adServer.bs

adServer.bs

186 ms

verify_selector.js

verify_selector.js

178 ms

blank.gif

blank.gif

182 ms

verifyr.js

verifyr.js

34 ms

client-verify.adtricity.com

client-verify.adtricity.com

347 ms

beacon.js

beacon.js

26 ms

0

0

11 ms

bg.png

bg.png

32 ms

adchoices.en.png

adchoices.en.png

59 ms

sd

sd

36 ms

Accessibility Review

ikiya.jp accessibility score

73

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

[aria-*] attributes do not match their roles

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: