Access 123trophy.jp. トロフィー・優勝カップ、表彰用品と記念品の123トロフィー

123trophy.jp screenshot

39

Performance

Renders faster than
60% of other websites
81

Accessibility

Visual factors better than
that of 52% of websites
67

Best Practices

More advanced features
available than in
24% of websites
93

SEO

Google-friendlier than
84% of websites

First Response

666 ms

Resources Loaded

27.2 sec

Page Rendered

1.4 sec

123trophy.jp screenshot

About Website

Visit 123trophy.jp now to see the best up-to-date 123 Trophy content and also check out these interesting facts you probably never knew about 123trophy.jp

トロフィー、優勝カップ、メダル等の表彰用品、マグカップ、携帯ストラップなど表彰用品・記念品の通信販売。名入れ彫刻のできるオリジナルオーダーメイドギフトなど表彰用品・記念品の取り扱い点数国内最大級

Visit 123trophy.jp

Key Findings

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

name

value

score

weighting

FCP (First Contentful Paint)

Value9.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value18.7 s

0/100

25%

SI (Speed Index)

Value14.9 s

1/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.195

63/100

15%

TTI (Time to Interactive)

Value16.3 s

5/100

10%

123trophy.jp

666 ms

www.123trophy.jp

2217 ms

def.css

506 ms

roll.js

711 ms

_a_cast.js

905 ms

Our browser made a total of 228 requests to load all elements on the main page. We found that 86% of them (195 requests) were addressed to the original 123trophy.jp, 4% (9 requests) were made to 123-trophy.biz and 3% (6 requests) were made to 123-trophy.com. The less responsive or slowest element that took the longest time to load (12.6 sec) belongs to the original domain 123trophy.jp.

Content Size

2.6 MB

After Optimization

2.4 MB

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

HTML Optimization

-80%

Potential reduce by 62.4 kB

Original 77.6 kB
After minification 73.3 kB
After compression 15.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 62.4 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 85.0 kB

Original 2.4 MB
After minification 2.3 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. 123 Trophy images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 34.2 kB

Original 111.2 kB
After minification 97.3 kB
After compression 77.0 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.2 kB or 31% of the original size.

CSS Optimization

-82%

Potential reduce by 9.4 kB

Original 11.5 kB
After minification 8.9 kB
After compression 2.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. 123trophy.jp needs all CSS files to be minified and compressed as it can save up to 9.4 kB or 82% of the original size.

Requests Now

223

After Optimization

148

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA input fields do not have accessible names

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.

High

<frame> or <iframe> elements do not have a title

High

Form elements do not have associated labels

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Document uses legible font sizes

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 123trophy.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 123trophy.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

123trophy.jp

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