Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

tomsj.com

トムス株式会社

Page Load Speed

4.1 sec in total

First Response

659 ms

Resources Loaded

3.3 sec

Page Rendered

164 ms

tomsj.com screenshot

About Website

Welcome to tomsj.com homepage info - get ready to check Tomsj best content for Hong Kong right away, or after learning these important things about tomsj.com

トムス株式会社の企業サイトです。トムスは、1万社以上に及ぶお客さまとのお取引を通して、日本全国に年間4,500万枚のウェアアイテムを提供しています。

Visit tomsj.com

Key Findings

We analyzed Tomsj.com page load time and found that the first response time was 659 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

tomsj.com performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value20.9 s

0/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.8 s

78/100

10%

Network Requests Diagram

tomsj.com

659 ms

import.css

345 ms

style_news.css

350 ms

jquery-1.3.1.js

1238 ms

yuga.js

531 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 96% of them (46 requests) were addressed to the original Tomsj.com, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Tomsj.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 151.0 kB (48%)

Content Size

311.6 kB

After Optimization

160.5 kB

In fact, the total size of Tomsj.com main page is 311.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. 15% of websites need less resources to load. Javascripts take 151.4 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 4.5 kB

  • Original 6.8 kB
  • After minification 6.3 kB
  • After compression 2.3 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 4.5 kB or 66% of the original size.

Image Optimization

-4%

Potential reduce by 4.6 kB

  • Original 114.4 kB
  • After minification 109.8 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. Tomsj images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 109.4 kB

  • Original 151.4 kB
  • After minification 101.9 kB
  • After compression 42.1 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 109.4 kB or 72% of the original size.

CSS Optimization

-84%

Potential reduce by 32.7 kB

  • Original 39.0 kB
  • After minification 27.5 kB
  • After compression 6.3 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. Tomsj.com needs all CSS files to be minified and compressed as it can save up to 32.7 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

47

After Optimization

8

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

Accessibility Review

tomsj.com accessibility score

100

Accessibility Issues

Best Practices

tomsj.com best practices score

83

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

SEO Factors

tomsj.com SEO score

92

Search Engine Optimization Advices

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

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 Tomsj.com 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 Tomsj.com 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 Tomsj. 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: