Tools & Wizards About Us
iword.co.jp screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

iword.co.jp

株式会社アイワード

Page Load Speed

8.5 sec in total

First Response

2.3 sec

Resources Loaded

6 sec

Page Rendered

167 ms

iword.co.jp screenshot

About Website

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

本づくりに、あたりまえを超えた驚きと感動を。株式会社アイワードは、札幌を拠点とし、従来の「印刷業」の技術を大切にしながら、「情報価値創造産業」への業界変革に取り組んでいます。

Visit iword.co.jp

Key Findings

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

Performance Metrics

iword.co.jp performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value27.3 s

0/100

25%

SI (Speed Index)

Value25.2 s

0/100

10%

TBT (Total Blocking Time)

Value1,140 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.334

34/100

15%

TTI (Time to Interactive)

Value32.0 s

0/100

10%

Network Requests Diagram

iword.co.jp

2280 ms

xoops.css

977 ms

1289 ms

index.php

868 ms

xoops.js

903 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 70% of them (32 requests) were addressed to the original Iword.co.jp, 26% (12 requests) were made to Iword-cojp.ssl-xserver.jp and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Iword.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 190.2 kB (28%)

Content Size

677.3 kB

After Optimization

487.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 18.0 kB

  • Original 21.8 kB
  • After minification 15.9 kB
  • After compression 3.8 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 5.9 kB, which is 27% 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 18.0 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 1.3 kB

  • Original 432.3 kB
  • After minification 431.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. Iword images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 149.2 kB

  • Original 195.6 kB
  • After minification 137.7 kB
  • After compression 46.4 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 149.2 kB or 76% of the original size.

CSS Optimization

-79%

Potential reduce by 21.7 kB

  • Original 27.6 kB
  • After minification 21.3 kB
  • After compression 5.9 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. Iword.co.jp needs all CSS files to be minified and compressed as it can save up to 21.7 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (39%)

Requests Now

44

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

iword.co.jp

iword.co.jp

2280 ms

xoops.css

xoops.css

977 ms

1289 ms

index.php

index.php

868 ms

xoops.js

xoops.js

903 ms

default.css

default.css

1016 ms

hdft.css

hdft.css

1054 ms

tab.css

tab.css

1097 ms

ui.tabs.css

ui.tabs.css

726 ms

jquery-1.2.6.js

jquery-1.2.6.js

1495 ms

ui.core.js

ui.core.js

755 ms

ui.tabs.js

ui.tabs.js

941 ms

mouseover.js

mouseover.js

902 ms

analytics.js

analytics.js

5 ms

collect

collect

11 ms

header_bg.gif

header_bg.gif

990 ms

leftnav00.gif

leftnav00.gif

365 ms

leftnav01.gif

leftnav01.gif

333 ms

leftnav02.gif

leftnav02.gif

344 ms

leftnav03.gif

leftnav03.gif

355 ms

digitaize2.jpg

digitaize2.jpg

1126 ms

banner_gd.png

banner_gd.png

749 ms

top_c_nav1.jpg

top_c_nav1.jpg

866 ms

top_c_nav2.jpg

top_c_nav2.jpg

892 ms

top_c_nav3.jpg

top_c_nav3.jpg

924 ms

top_c_nav4.jpg

top_c_nav4.jpg

918 ms

top_c_link01.gif

top_c_link01.gif

1122 ms

top_c_link02.gif

top_c_link02.gif

1361 ms

nav011.gif

nav011.gif

424 ms

nav021.gif

nav021.gif

370 ms

nav031.gif

nav031.gif

188 ms

nav041.gif

nav041.gif

519 ms

nav051.gif

nav051.gif

178 ms

img01.jpg

img01.jpg

1309 ms

img02.jpg

img02.jpg

918 ms

img03.jpg

img03.jpg

930 ms

img04.jpg

img04.jpg

1068 ms

img05.jpg

img05.jpg

1228 ms

navbg.gif

navbg.gif

870 ms

tab.png

tab.png

2570 ms

header_logo.gif

header_logo.gif

925 ms

tel01.gif

tel01.gif

589 ms

tel02.gif

tel02.gif

597 ms

leftnav00.gif

leftnav00.gif

624 ms

footer_bg.gif

footer_bg.gif

636 ms

listmk.gif

listmk.gif

1179 ms

Accessibility Review

iword.co.jp accessibility score

63

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

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

iword.co.jp best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

iword.co.jp SEO score

83

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

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iword.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 Iword.co.jp main page’s claimed encoding is euc-jp. 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

iword.co.jp

Open Graph data is detected on the main page of Iword. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: