Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

office-com.jp

オフィス家具通販の【オフィスコム】

Page Load Speed

10 sec in total

First Response

374 ms

Resources Loaded

9 sec

Page Rendered

597 ms

office-com.jp screenshot

About Website

Click here to check amazing Office Com content for Japan. Otherwise, check out these important facts you probably never knew about office-com.jp

オフィス家具19万点以上の品揃えで、お客様の「簡単に最安で最速のかっこいいオフィスづくり」を実現します。送料無料で最速翌日にお届け!各種帳票対応、全国ショールーム展開中!

Visit office-com.jp

Key Findings

We analyzed Office-com.jp page load time and found that the first response time was 374 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

office-com.jp performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value1,830 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value20.2 s

2/100

10%

Network Requests Diagram

office-com.jp

374 ms

www.office-com.jp

1306 ms

reset.min.css

291 ms

common.min.css

486 ms

contents.min.css

826 ms

Our browser made a total of 233 requests to load all elements on the main page. We found that 80% of them (186 requests) were addressed to the original Office-com.jp, 4% (10 requests) were made to D.adroll.com and 1% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Office-com.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 445.0 kB (18%)

Content Size

2.4 MB

After Optimization

2.0 MB

In fact, the total size of Office-com.jp main page is 2.4 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. 70% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 63.3 kB

  • Original 81.8 kB
  • After minification 73.2 kB
  • After compression 18.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. This page needs HTML code to be minified as it can gain 8.6 kB, which is 11% 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 63.3 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 5.5 kB

  • Original 1.7 MB
  • After minification 1.7 MB

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. Office Com images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 269.5 kB

  • Original 486.7 kB
  • After minification 486.7 kB
  • After compression 217.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 269.5 kB or 55% of the original size.

CSS Optimization

-80%

Potential reduce by 106.6 kB

  • Original 132.8 kB
  • After minification 132.6 kB
  • After compression 26.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. Office-com.jp needs all CSS files to be minified and compressed as it can save up to 106.6 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 73 (34%)

Requests Now

217

After Optimization

144

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

Accessibility Review

office-com.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-*] attributes do not have valid values

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

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

office-com.jp best practices score

83

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

Low

Detected JavaScript libraries

SEO Factors

office-com.jp SEO score

76

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

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 Office-com.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 Office-com.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

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