Tools & Wizards About Us
sony.co.jp screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

sony.co.jp

ソニー株式会社 | ホーム

Page Load Speed

2.9 sec in total

First Response

90 ms

Resources Loaded

2.7 sec

Page Rendered

124 ms

sony.co.jp screenshot

About Website

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

ソニー株式会社のポータルサイトです。ソニーグループ内のエンタテインメント・テクノロジー&サービス（ET&S）事業分野の企業情報、製品・サービス情報、お知らせとニュースリリース、サステナビリティ、採用情報などをご覧いただけます。

Visit sony.co.jp

Key Findings

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

Performance Metrics

sony.co.jp performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value17.1 s

0/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value5,000 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.312

37/100

15%

TTI (Time to Interactive)

Value18.3 s

3/100

10%

Network Requests Diagram

sony.co.jp

90 ms

www.sony.co.jp

181 ms

TweenMax.min.js

152 ms

jquery-3.6.0.min.js

271 ms

jquery.easing.1.3.js

222 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 30% of them (23 requests) were addressed to the original Sony.co.jp, 21% (16 requests) were made to Fast.fonts.net and 9% (7 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Sony.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 202.3 kB (13%)

Content Size

1.6 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sony.co.jp main page is 1.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 86.0 kB

  • Original 105.9 kB
  • After minification 95.5 kB
  • After compression 19.9 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 86.0 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 1.6 kB

  • Original 1.2 MB
  • After minification 1.2 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. Sony images are well optimized though.

JavaScript Optimization

-34%

Potential reduce by 80.3 kB

  • Original 236.8 kB
  • After minification 228.8 kB
  • After compression 156.5 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 80.3 kB or 34% of the original size.

CSS Optimization

-55%

Potential reduce by 34.4 kB

  • Original 62.6 kB
  • After minification 55.4 kB
  • After compression 28.2 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. Sony.co.jp needs all CSS files to be minified and compressed as it can save up to 34.4 kB or 55% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (50%)

Requests Now

72

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sony.co.jp

sony.co.jp

90 ms

www.sony.co.jp

www.sony.co.jp

181 ms

TweenMax.min.js

TweenMax.min.js

152 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

271 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

222 ms

jquery.cookie.js

jquery.cookie.js

202 ms

includeCommon.js

includeCommon.js

218 ms

tile.js

tile.js

331 ms

reset.css

reset.css

263 ms

swiper.min.css

swiper.min.css

181 ms

853bfcd2-9633-4789-ab90-6ec62910a568.js

853bfcd2-9633-4789-ab90-6ec62910a568.js

188 ms

common.js

common.js

244 ms

search_resp_jp.css

search_resp_jp.css

428 ms

jquery.min.js

jquery.min.js

188 ms

slick.min.js

slick.min.js

188 ms

picturefill.js

picturefill.js

184 ms

top3.js

top3.js

505 ms

slick.css

slick.css

180 ms

index3.css

index3.css

393 ms

s_code.js

s_code.js

458 ms

sc_ppv.js

sc_ppv.js

744 ms

gtid

gtid

304 ms

mfx-serp.css

mfx-serp.css

8 ms

mfx-serp-resp.css

mfx-serp-resp.css

8 ms

mfx-sbox.js

mfx-sbox.js

6 ms

font-awesome.css

font-awesome.css

15 ms

gtm.js

gtm.js

175 ms

P7XN4-V2TSB-2T8M6-FRSJA-ZK3CZ

P7XN4-V2TSB-2T8M6-FRSJA-ZK3CZ

493 ms

extsync

extsync

1113 ms

logo.svg

logo.svg

164 ms

slider_img-231129MV1_PC@2x.jpg

slider_img-231129MV1_PC@2x.jpg

1785 ms

slider_img-231208MV5_PC@2x.jpg

slider_img-231208MV5_PC@2x.jpg

618 ms

slider_img-231122MV3_PC@2x.jpg

slider_img-231122MV3_PC@2x.jpg

1109 ms

slider_img-231215MV4_PC@2x.jpg

slider_img-231215MV4_PC@2x.jpg

165 ms

slider_img-231227MV5_PC@2x.jpg

slider_img-231227MV5_PC@2x.jpg

876 ms

ico-info@2x.png

ico-info@2x.png

616 ms

tmpl_footer_grouplink.png

tmpl_footer_grouplink.png

477 ms

js

js

290 ms

js

js

426 ms

analytics.js

analytics.js

421 ms

df549e883e793380_4254.js

df549e883e793380_4254.js

715 ms

otf_1336080OTFFeatDisabled.js

otf_1336080OTFFeatDisabled.js

540 ms

otf_1336082OTFFeatDisabled.js

otf_1336082OTFFeatDisabled.js

582 ms

otf_1336070OTFFeatDisabled.js

otf_1336070OTFFeatDisabled.js

641 ms

otf_1336072OTFFeatDisabled.js

otf_1336072OTFFeatDisabled.js

601 ms

otf_1336078OTFFeatDisabled.js

otf_1336078OTFFeatDisabled.js

600 ms

otf_1336068OTFFeatDisabled.js

otf_1336068OTFFeatDisabled.js

640 ms

otf_1336074OTFFeatDisabled.js

otf_1336074OTFFeatDisabled.js

639 ms

otf_1336076OTFFeatDisabled.js

otf_1336076OTFFeatDisabled.js

678 ms

otf_1336054OTFFeatDisabled.js

otf_1336054OTFFeatDisabled.js

683 ms

otf_1336056OTFFeatDisabled.js

otf_1336056OTFFeatDisabled.js

683 ms

otf_1336064OTFFeatDisabled.js

otf_1336064OTFFeatDisabled.js

682 ms

otf_1336066OTFFeatDisabled.js

otf_1336066OTFFeatDisabled.js

683 ms

otf_1336058OTFFeatDisabled.js

otf_1336058OTFFeatDisabled.js

680 ms

otf_1346724OTFFeatDisabled.js

otf_1346724OTFFeatDisabled.js

726 ms

ico_search.svg

ico_search.svg

454 ms

509e2a7d-d453-44aa-a0b2-8cb7fb111da7.woff

509e2a7d-d453-44aa-a0b2-8cb7fb111da7.woff

873 ms

FontSubsetter.ashx

FontSubsetter.ashx

878 ms

FontSubsetter.ashx

FontSubsetter.ashx

594 ms

config.json

config.json

444 ms

collect

collect

212 ms

collect

collect

222 ms

collect

collect

197 ms

collect

collect

198 ms

tracking.min.js

tracking.min.js

153 ms

td.min.js

td.min.js

185 ms

dd

dd

426 ms

s58902026771102

s58902026771102

44 ms

collect

collect

79 ms

js

js

109 ms

collect

collect

356 ms

js

js

107 ms

js

js

354 ms

collect

collect

341 ms

js

js

342 ms

ga-audiences

ga-audiences

430 ms

get_cookie_id

get_cookie_id

123 ms

Accessibility Review

sony.co.jp accessibility score

90

Accessibility Issues

ARIA

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.

Impact

Issue

High

[aria-*] attributes do not match their roles

Best Practices

sony.co.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

sony.co.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

    JA

  • Encoding

    UTF-8

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

sony.co.jp

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