Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

oaland.jp

コピー機・複合機のOAランド / 公式サイト

Page Load Speed

10.4 sec in total

First Response

336 ms

Resources Loaded

9.5 sec

Page Rendered

532 ms

oaland.jp screenshot

About Website

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

起業家総合支援のOAランド公式サイトはこちら。コピー機やビジネスフォンなどのOA機器やオフィス家具を中心に全国販売。オフィス作りをトータルサポート。

Visit oaland.jp

Key Findings

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

Performance Metrics

oaland.jp performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

2/100

10%

LCP (Largest Contentful Paint)

Value14.4 s

0/100

25%

SI (Speed Index)

Value14.9 s

1/100

10%

TBT (Total Blocking Time)

Value1,920 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.163

72/100

15%

TTI (Time to Interactive)

Value29.3 s

0/100

10%

Network Requests Diagram

oaland.jp

336 ms

www.oaland.jp

3982 ms

import.css

379 ms

js

52 ms

css.js

495 ms

Our browser made a total of 191 requests to load all elements on the main page. We found that 64% of them (122 requests) were addressed to the original Oaland.jp, 14% (27 requests) were made to Static.xx.fbcdn.net and 8% (16 requests) were made to Scontent-iad3-2.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Oaland.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 267.8 kB (8%)

Content Size

3.4 MB

After Optimization

3.1 MB

In fact, the total size of Oaland.jp main page is 3.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 86.5 kB

  • Original 108.6 kB
  • After minification 102.6 kB
  • After compression 22.1 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 86.5 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 40.2 kB

  • Original 2.9 MB
  • After minification 2.9 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. Oaland images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 14.4 kB

  • Original 183.5 kB
  • After minification 181.0 kB
  • After compression 169.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-72%

Potential reduce by 126.7 kB

  • Original 176.6 kB
  • After minification 114.3 kB
  • After compression 49.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. Oaland.jp needs all CSS files to be minified and compressed as it can save up to 126.7 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 106 (57%)

Requests Now

187

After Optimization

81

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

Accessibility Review

oaland.jp accessibility score

56

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

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

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

oaland.jp best practices score

50

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

oaland.jp SEO score

83

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 uses 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 Oaland.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 Oaland.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 data is detected on the main page of Oaland. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: