Report Summary

  • 74

    Performance

    Renders faster than
    84% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

tomos.co.jp

ちりめん亭

Page Load Speed

5.4 sec in total

First Response

398 ms

Resources Loaded

4.6 sec

Page Rendered

481 ms

tomos.co.jp screenshot

About Website

Visit tomos.co.jp now to see the best up-to-date Tomos content for Japan and also check out these interesting facts you probably never knew about tomos.co.jp

Visit tomos.co.jp

Key Findings

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

Performance Metrics

tomos.co.jp performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value14.5 s

0/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value1.0 s

100/100

10%

Network Requests Diagram

tomos.co.jp

398 ms

common.css

190 ms

common.js

368 ms

bg_body.gif

191 ms

bg_wrap.gif

184 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that all of those requests were addressed to Tomos.co.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Tomos.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 85.5 kB (5%)

Content Size

1.7 MB

After Optimization

1.6 MB

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

HTML Optimization

-76%

Potential reduce by 5.2 kB

  • Original 6.9 kB
  • After minification 5.6 kB
  • After compression 1.7 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 1.3 kB, which is 19% 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 5.2 kB or 76% of the original size.

Image Optimization

-5%

Potential reduce by 77.6 kB

  • Original 1.7 MB
  • After minification 1.6 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. Tomos images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 611 B

  • Original 1.1 kB
  • After minification 946 B
  • After compression 452 B

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 611 B or 57% of the original size.

CSS Optimization

-74%

Potential reduce by 2.0 kB

  • Original 2.7 kB
  • After minification 2.2 kB
  • After compression 703 B

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. Tomos.co.jp needs all CSS files to be minified and compressed as it can save up to 2.0 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (33%)

Requests Now

33

After Optimization

22

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

Accessibility Review

tomos.co.jp accessibility score

59

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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>).

Best Practices

tomos.co.jp best practices score

67

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

SEO Factors

tomos.co.jp SEO score

58

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tomos.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Tomos.co.jp main page’s claimed encoding is shift_jis. 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

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