Report Summary

  • 53

    Performance

    Renders faster than
    71% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

uni-std.co.jp

ユニバーサルスタンダード株式会社(ユニスター)

Page Load Speed

3.6 sec in total

First Response

556 ms

Resources Loaded

2.9 sec

Page Rendered

190 ms

uni-std.co.jp screenshot

About Website

Welcome to uni-std.co.jp homepage info - get ready to check Uni Std best content right away, or after learning these important things about uni-std.co.jp

ユニバーサルスタンダードはテレビショッピングおよび各種通販媒体に強いネットワークを持つ通販卸です。弊社が持つ魅力的な商品および通信販売のネットワークをご紹介します。テレビショッピングなどの通信販売を通して『感動的な新しい価値の提供』を一緒に実現できる人材と商品を幅広く求めています。

Visit uni-std.co.jp

Key Findings

We analyzed Uni-std.co.jp page load time and found that the first response time was 556 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

uni-std.co.jp performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value14.3 s

1/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

uni-std.co.jp

556 ms

base.css

177 ms

top.css

352 ms

jquery-1.4.2.min.js

726 ms

easing.js

374 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 67% of them (40 requests) were addressed to the original Uni-std.co.jp, 13% (8 requests) were made to Apis.google.com and 5% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Uni-std.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 87.3 kB (12%)

Content Size

730.6 kB

After Optimization

643.3 kB

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

HTML Optimization

-69%

Potential reduce by 17.0 kB

  • Original 24.5 kB
  • After minification 23.6 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 17.0 kB or 69% of the original size.

Image Optimization

-1%

Potential reduce by 5.0 kB

  • Original 591.6 kB
  • After minification 586.6 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. Uni Std images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 60.9 kB

  • Original 108.3 kB
  • After minification 103.2 kB
  • After compression 47.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 60.9 kB or 56% of the original size.

CSS Optimization

-72%

Potential reduce by 4.5 kB

  • Original 6.2 kB
  • After minification 5.4 kB
  • After compression 1.7 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. Uni-std.co.jp needs all CSS files to be minified and compressed as it can save up to 4.5 kB or 72% of the original size.

Requests Breakdown

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

Requests Now

59

After Optimization

33

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

Accessibility Review

uni-std.co.jp accessibility score

82

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.

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

Links do not have a discernible name

Best Practices

uni-std.co.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

uni-std.co.jp SEO score

89

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

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 Uni-std.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 Uni-std.co.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 Uni Std. 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: