Tools & Wizards About Us
trinus.jp screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

trinus.jp

TRINUS (トリナス) | プロダクト共創プラットフォーム

Page Load Speed

5.2 sec in total

First Response

718 ms

Resources Loaded

4.2 sec

Page Rendered

313 ms

trinus.jp screenshot

About Website

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

技術とデザインのマッチングやクラウドファンディングを通じて「未来の日常生活品」を共創するものづくりプラットフォームです。

Visit trinus.jp

Key Findings

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

Performance Metrics

trinus.jp performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value3,390 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.264

46/100

15%

TTI (Time to Interactive)

Value93.8 s

0/100

10%

Network Requests Diagram

trinus.jp

718 ms

application-18e7d3272e37d02231fb7fcfd199471b.css

445 ms

application-551e9001dd9a21bd3482418b57588d94.js

746 ms

top-182dd52fd604e620089f93d234dcb513.js

465 ms

thumb_1200x675_20151205213033.png

847 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 39% of them (13 requests) were addressed to the original Trinus.jp, 55% (18 requests) were made to Trinus.s3.amazonaws.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Trinus.s3.amazonaws.com.

Page Optimization Overview & Recommendations

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

Content Size

4.0 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 18.0 kB

  • Original 22.7 kB
  • After minification 21.6 kB
  • After compression 4.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. 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 18.0 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 153.7 kB

  • Original 3.6 MB
  • After minification 3.4 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. TRINUS images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 109.5 kB

  • Original 183.7 kB
  • After minification 183.7 kB
  • After compression 74.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.5 kB or 60% of the original size.

CSS Optimization

-85%

Potential reduce by 194.7 kB

  • Original 227.8 kB
  • After minification 225.6 kB
  • After compression 33.1 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. Trinus.jp needs all CSS files to be minified and compressed as it can save up to 194.7 kB or 85% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

32

After Optimization

32

  • Images
  • JavaScript
  • CSS

The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TRINUS. According to our analytics all requests are already optimized.

Network Requests Diagram

trinus.jp

trinus.jp

718 ms

application-18e7d3272e37d02231fb7fcfd199471b.css

application-18e7d3272e37d02231fb7fcfd199471b.css

445 ms

application-551e9001dd9a21bd3482418b57588d94.js

application-551e9001dd9a21bd3482418b57588d94.js

746 ms

top-182dd52fd604e620089f93d234dcb513.js

top-182dd52fd604e620089f93d234dcb513.js

465 ms

thumb_1200x675_20151205213033.png

thumb_1200x675_20151205213033.png

847 ms

thumb_1200x675_20150805205445.jpg

thumb_1200x675_20150805205445.jpg

2018 ms

thumb_720x480_20141214025152.jpg

thumb_720x480_20141214025152.jpg

1443 ms

thumb_720x480_20151202130421.jpg

thumb_720x480_20151202130421.jpg

1425 ms

thumb_720x480_20141217141045.JPG

thumb_720x480_20141217141045.JPG

1449 ms

thumb_720x480_20150105233701.jpg

thumb_720x480_20150105233701.jpg

1503 ms

thumb_720x480_20150207010943.jpg

thumb_720x480_20150207010943.jpg

1714 ms

thumb_720x480_20150115123626.jpg

thumb_720x480_20150115123626.jpg

1777 ms

thumb_720x480_20150103154715.png

thumb_720x480_20150103154715.png

2210 ms

thumb_720x480_20150112041024.png

thumb_720x480_20150112041024.png

1798 ms

thumb_720x480_20150821215451.jpg

thumb_720x480_20150821215451.jpg

1684 ms

thumb_720x480_20141228222956.png

thumb_720x480_20141228222956.png

2022 ms

thumb_720x480_20150116232826.jpg

thumb_720x480_20150116232826.jpg

2356 ms

thumb_720x480_20150101212712.png

thumb_720x480_20150101212712.png

2125 ms

thumb_720x480_20151018220401.jpg

thumb_720x480_20151018220401.jpg

2127 ms

thumb_720x480_20150113225426.jpg

thumb_720x480_20150113225426.jpg

2371 ms

thumb_720x480_20150414232558.jpg

thumb_720x480_20150414232558.jpg

2223 ms

thumb_720x480_20150116003916.jpg

thumb_720x480_20150116003916.jpg

2319 ms

pub_top_h1-dcf28222ddfb4da2051e6e266b73c295.png

pub_top_h1-dcf28222ddfb4da2051e6e266b73c295.png

298 ms

pub_top_main_copy-af6ef75ff58246304ab30a3e23ea6b33.png

pub_top_main_copy-af6ef75ff58246304ab30a3e23ea6b33.png

447 ms

logo_03_16px_trans_light@2x-1cc9d466eb055ed8dddfd1889c0bb18b.png

logo_03_16px_trans_light@2x-1cc9d466eb055ed8dddfd1889c0bb18b.png

182 ms

sns_google_plus_32px_light@2x-c9d372dfcee198fe8deb61b4a921f295.png

sns_google_plus_32px_light@2x-c9d372dfcee198fe8deb61b4a921f295.png

346 ms

sns_facebook_32px_light@2x-cbff8ace37835371509d5b55f29d86c6.png

sns_facebook_32px_light@2x-cbff8ace37835371509d5b55f29d86c6.png

446 ms

logo_04_32px_trans_light@2x-a8e89078d5d19493e8d05ec21b80e2a4.png

logo_04_32px_trans_light@2x-a8e89078d5d19493e8d05ec21b80e2a4.png

490 ms

icons_24-4b9d293b31dd439fa733146f63ac9c76.png

icons_24-4b9d293b31dd439fa733146f63ac9c76.png

631 ms

common_list_head_01-e7bd7e72ca12ada799b572a377d86cc3.png

common_list_head_01-e7bd7e72ca12ada799b572a377d86cc3.png

497 ms

analytics.js

analytics.js

24 ms

bx_loader-5e823b16dd41e77e46c50b372d5a2fdf.gif

bx_loader-5e823b16dd41e77e46c50b372d5a2fdf.gif

451 ms

collect

collect

11 ms

Accessibility Review

trinus.jp accessibility score

83

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

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

Links do not have a discernible name

Best Practices

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

trinus.jp SEO score

91

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trinus.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 Trinus.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

trinus.jp

Open Graph data is detected on the main page of TRINUS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: