Tools & Wizards About Us
ibos.co.jp screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

ibos.co.jp

アイボスASPサービス

Page Load Speed

5.8 sec in total

First Response

802 ms

Resources Loaded

4.7 sec

Page Rendered

313 ms

ibos.co.jp screenshot

About Website

Click here to check amazing Ibos content. Otherwise, check out these important facts you probably never knew about ibos.co.jp

印刷編集ツールのASPサービスなら「アイボス」へ。ネットで印刷物のデザインが自分で簡単に作成出来て即注文できるツールをご提供。制作コストの大幅削減の決定版です。

Visit ibos.co.jp

Key Findings

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

Performance Metrics

ibos.co.jp performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.1 s

100/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.1 s

100/100

10%

Network Requests Diagram

ibos.co.jp

802 ms

top1602.css

1096 ms

common1602.css

756 ms

calender1602.css

783 ms

slide1602.css

950 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 64% of them (49 requests) were addressed to the original Ibos.co.jp, 5% (4 requests) were made to Seal.alphassl.com and 5% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Ibos.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 439.1 kB (42%)

Content Size

1.0 MB

After Optimization

606.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-65%

Potential reduce by 14.0 kB

  • Original 21.5 kB
  • After minification 21.2 kB
  • After compression 7.5 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 14.0 kB or 65% of the original size.

Image Optimization

-4%

Potential reduce by 21.0 kB

  • Original 477.9 kB
  • After minification 457.0 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. Ibos images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 182.9 kB

  • Original 279.1 kB
  • After minification 254.7 kB
  • After compression 96.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 182.9 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 221.2 kB

  • Original 266.8 kB
  • After minification 258.8 kB
  • After compression 45.6 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. Ibos.co.jp needs all CSS files to be minified and compressed as it can save up to 221.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (26%)

Requests Now

69

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ibos.co.jp

ibos.co.jp

802 ms

top1602.css

top1602.css

1096 ms

common1602.css

common1602.css

756 ms

calender1602.css

calender1602.css

783 ms

slide1602.css

slide1602.css

950 ms

gotop.js

gotop.js

816 ms

jquery.min.js

jquery.min.js

50 ms

jquery.flexslider.js

jquery.flexslider.js

1603 ms

jsapi

jsapi

63 ms

alpha_image_115-55_ja.js

alpha_image_115-55_ja.js

18 ms

ga.js

ga.js

211 ms

Cu1WN97D4KY

Cu1WN97D4KY

296 ms

cvs_l.gif

cvs_l.gif

1603 ms

alpha_noscript_115-55_ja.gif

alpha_noscript_115-55_ja.gif

253 ms

toplogo.gif

toplogo.gif

253 ms

top-tel.png

top-tel.png

458 ms

navi02-1.gif

navi02-1.gif

286 ms

navi02-2.gif

navi02-2.gif

254 ms

topmenu01.png

topmenu01.png

457 ms

topmenu02.png

topmenu02.png

456 ms

topmenu03.png

topmenu03.png

458 ms

topmenu04.png

topmenu04.png

456 ms

topmenu05.png

topmenu05.png

457 ms

topmenu06.png

topmenu06.png

630 ms

slide3.jpg

slide3.jpg

1851 ms

slide2.jpg

slide2.jpg

1768 ms

slide1.jpg

slide1.jpg

1541 ms

tokucho1.gif

tokucho1.gif

659 ms

tokucho2.gif

tokucho2.gif

851 ms

tokucho3.gif

tokucho3.gif

814 ms

point1.gif

point1.gif

862 ms

point2.gif

point2.gif

1034 ms

point3.gif

point3.gif

1027 ms

point4.gif

point4.gif

1061 ms

point5.gif

point5.gif

1166 ms

site1.GIF

site1.GIF

1377 ms

site2.GIF

site2.GIF

1428 ms

site3.GIF

site3.GIF

1353 ms

category1.GIF

category1.GIF

1542 ms

category2.GIF

category2.GIF

1563 ms

category3.GIF

category3.GIF

1611 ms

category4.GIF

category4.GIF

1711 ms

category5.GIF

category5.GIF

1723 ms

category7.GIF

category7.GIF

2099 ms

category8.GIF

category8.GIF

1968 ms

category9.GIF

category9.GIF

1889 ms

category10.GIF

category10.GIF

1904 ms

category11.GIF

category11.GIF

1940 ms

category13.GIF

category13.GIF

2026 ms

atobarai.gif

atobarai.gif

1915 ms

widgets.js

widgets.js

141 ms

__utm.gif

__utm.gif

44 ms

creditcard.gif

creditcard.gif

1852 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

108 ms

www-embed-player.js

www-embed-player.js

135 ms

side-banner01.gif

side-banner01.gif

1873 ms

side-banner02.gif

side-banner02.gif

1885 ms

collect

collect

189 ms

siteSeal.do

siteSeal.do

424 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

222 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

31 ms

ad_status.js

ad_status.js

103 ms

submenu-icon.png

submenu-icon.png

1771 ms

side-banner03.gif

side-banner03.gif

1823 ms

printer.jpg

printer.jpg

2008 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

96 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

110 ms

ga-audiences

ga-audiences

59 ms

syndication

syndication

102 ms

704588994558832640

704588994558832640

201 ms

siteSealImage.do

siteSealImage.do

242 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

32 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

134 ms

rlqCifRU_normal.jpg

rlqCifRU_normal.jpg

176 ms

jot

jot

27 ms

cvs_l.gif

cvs_l.gif

995 ms

Accessibility Review

ibos.co.jp accessibility score

73

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

Image elements do not have [alt] attributes

Best Practices

ibos.co.jp best practices score

67

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

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

ibos.co.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

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 Ibos.co.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 Ibos.co.jp 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

ibos.co.jp

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