Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

t-r-a-m.jp

サイト制作・アプリ開発|株式会社トラム|デジタルマーケティングからクリエイティブ制作まで一貫してサービス提供

Page Load Speed

5.4 sec in total

First Response

759 ms

Resources Loaded

3.9 sec

Page Rendered

683 ms

t-r-a-m.jp screenshot

About Website

Click here to check amazing T R A M content. Otherwise, check out these important facts you probably never knew about t-r-a-m.jp

【想像力×創造力】 私たちは、人の気持ちを想像し、気持ちを動かすクリエイティブを創ります。

Visit t-r-a-m.jp

Key Findings

We analyzed T-r-a-m.jp page load time and found that the first response time was 759 ms and then it took 4.6 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

t-r-a-m.jp performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value19.7 s

0/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value6.1 s

64/100

10%

Network Requests Diagram

t-r-a-m.jp

759 ms

styles.css

680 ms

jquery.min.js

51 ms

common.js

355 ms

jquery.easy-rollover.js

359 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 90% of them (61 requests) were addressed to the original T-r-a-m.jp, 4% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain T-r-a-m.jp.

Page Optimization Overview & Recommendations

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

Content Size

1.7 MB

After Optimization

1.5 MB

In fact, the total size of T-r-a-m.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. 40% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 7.2 kB

  • Original 10.4 kB
  • After minification 9.5 kB
  • After compression 3.2 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 7.2 kB or 69% of the original size.

Image Optimization

-8%

Potential reduce by 136.5 kB

  • Original 1.6 MB
  • After minification 1.5 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. T R A M images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 34.5 kB

  • Original 56.4 kB
  • After minification 54.9 kB
  • After compression 21.8 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 34.5 kB or 61% of the original size.

CSS Optimization

-85%

Potential reduce by 17.1 kB

  • Original 20.2 kB
  • After minification 14.6 kB
  • After compression 3.0 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. T-r-a-m.jp needs all CSS files to be minified and compressed as it can save up to 17.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (14%)

Requests Now

64

After Optimization

55

The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of T R A M. 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 as a result speed up the page load time.

Accessibility Review

t-r-a-m.jp accessibility score

71

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.

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

Best Practices

t-r-a-m.jp best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

t-r-a-m.jp SEO score

84

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 T-r-a-m.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 T-r-a-m.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 T R A M. 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: