Tools & Wizards About Us
trinus.jp screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    53% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 81% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

trinus.jp

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

Page Load Speed

1.1 sec in total

First Response

276 ms

Resources Loaded

659 ms

Page Rendered

196 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 276 ms and then it took 855 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

trinus.jp performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value940 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value26.0 s

0/100

10%

Network Requests Diagram

trinus.jp

276 ms

constants.js

20 ms

pubsub.js

34 ms

global.js

35 ms

animations.js

34 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 49.1 kB (17%)

Content Size

296.6 kB

After Optimization

247.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 44.8 kB

  • Original 61.3 kB
  • After minification 60.2 kB
  • After compression 16.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 44.8 kB or 73% of the original size.

Image Optimization

-3%

Potential reduce by 2.9 kB

  • Original 109.7 kB
  • After minification 106.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. TRINUS images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 235 B

  • Original 104.1 kB
  • After minification 104.1 kB
  • After compression 103.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-5%

Potential reduce by 1.2 kB

  • Original 21.5 kB
  • After minification 21.5 kB
  • After compression 20.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. Trinus.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (88%)

Requests Now

32

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

trinus.jp

trinus.jp

276 ms

constants.js

constants.js

20 ms

pubsub.js

pubsub.js

34 ms

global.js

global.js

35 ms

animations.js

animations.js

34 ms

preloads.js

preloads.js

48 ms

load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js

load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js

33 ms

storefront-80e528be853eac23af2454534897ca9536b1d3d04aa043b042f34879a3c111c8.js

storefront-80e528be853eac23af2454534897ca9536b1d3d04aa043b042f34879a3c111c8.js

36 ms

features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js

features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js

53 ms

scripts.js

scripts.js

52 ms

base.css

base.css

53 ms

shopify-perf-kit-unstable.min.js

shopify-perf-kit-unstable.min.js

45 ms

details-disclosure.js

details-disclosure.js

51 ms

details-modal.js

details-modal.js

68 ms

cart-notification.js

cart-notification.js

62 ms

search-form.js

search-form.js

66 ms

section-image-banner.css

section-image-banner.css

65 ms

section-rich-text.css

section-rich-text.css

71 ms

section-footer.css

section-footer.css

74 ms

component-newsletter.css

component-newsletter.css

78 ms

component-list-menu.css

component-list-menu.css

83 ms

component-list-payment.css

component-list-payment.css

86 ms

component-list-social.css

component-list-social.css

88 ms

trekkie.storefront.72278931d43be9cf54de64f928f82f2eef1fa047.min.js

trekkie.storefront.72278931d43be9cf54de64f928f82f2eef1fa047.min.js

59 ms

shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js

shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js

36 ms

shopify-boomerang-1.0.0.min.js

shopify-boomerang-1.0.0.min.js

57 ms

lab_produce_logo_35f92ac0-b25c-450a-ba58-97bf9e8b67af.png

lab_produce_logo_35f92ac0-b25c-450a-ba58-97bf9e8b67af.png

57 ms

09a1ab0c841f8c8f051f1da001a5f406.jpg

09a1ab0c841f8c8f051f1da001a5f406.jpg

55 ms

component-search.css

component-search.css

22 ms

component-menu-drawer.css

component-menu-drawer.css

20 ms

component-cart-notification.css

component-cart-notification.css

20 ms

component-cart-items.css

component-cart-items.css

21 ms

component-mega-menu.css

component-mega-menu.css

17 ms

Accessibility Review

trinus.jp accessibility score

93

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

Links do not have a discernible name

Best Practices

trinus.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

trinus.jp SEO score

100

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 uses legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    EN

  • 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 it does not match the claimed English language. 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: