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

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.6 s

0/100

25%

SI (Speed Index)

Value15.4 s

1/100

10%

TBT (Total Blocking Time)

Value250 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.187

65/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

123photo.jp

1045 ms

common.css

974 ms

jsonp.js

987 ms

_a_cast.js

972 ms

jquery.min.js

34 ms

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

Content Size

1.2 MB

After Optimization

1.1 MB

In fact, the total size of 123photo.jp main page is 1.2 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.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 33.1 kB

Original 43.5 kB
After minification 39.8 kB
After compression 10.4 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 33.1 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 40.9 kB

Original 1.1 MB
After minification 1.1 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 Photo images are well optimized though.

JavaScript Optimization

-39%

Potential reduce by 29.0 kB

Original 74.7 kB
After minification 64.0 kB
After compression 45.7 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 29.0 kB or 39% of the original size.

CSS Optimization

-79%

Potential reduce by 7.6 kB

Original 9.7 kB
After minification 7.3 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. 123photo.jp needs all CSS files to be minified and compressed as it can save up to 7.6 kB or 79% of the original size.

Requests Now

115

After Optimization

The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 123 Photo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 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-hidden="true"] elements contain focusable descendents

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

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

123photo.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

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

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

123photo.jp

common.css

jsonp.js

_a_cast.js

jquery.min.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

123photo.jp

common.css

jsonp.js

_a_cast.js

jquery.min.js

top.js

top.css

shortest_send_date.js

ppz.js

ppz_draw.js

acItemview.js

ppz_clip.js

conversion.js

gtm.js

b-data230.jpg

bn_cu191.gif

bn_wp191.gif

bn_b191p.gif

lbl_photo_sale.gif

back.jpg

newhead01.gif

hm01.gif

hm02.gif

hm03.gif

hm04.gif

hm05.gif

hm06-2.gif

hm07.gif

bn-head01.jpg

bn-head02.jpg

bn-head03.jpg

sbn-touroku.jpg

s-my01.jpg

s-my02.jpg

s-my03.jpg

s-my04.jpg

bn_phot_amazon.gif

leftmenu01.jpg

sbn-menu.jpg

sbn-display.jpg

sbn-interia.jpg

photo.gif

leftmenu02.jpg