Tools & Wizards About Us
sony.co.jp screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

sony.co.jp

ソニー株式会社 | ホーム

Page Load Speed

8 sec in total

First Response

127 ms

Resources Loaded

7.5 sec

Page Rendered

303 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 127 ms and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

sony.co.jp performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

3/100

10%

LCP (Largest Contentful Paint)

Value19.3 s

0/100

25%

SI (Speed Index)

Value15.4 s

0/100

10%

TBT (Total Blocking Time)

Value7,200 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.392

26/100

15%

TTI (Time to Interactive)

Value21.5 s

1/100

10%

Network Requests Diagram

sony.co.jp

127 ms

sony.co.jp

19 ms

www.sony.co.jp

159 ms

TweenMax.min.js

48 ms

jquery-3.6.0.min.js

276 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 58% of them (53 requests) were addressed to the original Sony.co.jp, 8% (7 requests) were made to Googletagmanager.com and 5% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Sony.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 110.3 kB (4%)

Content Size

2.8 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 82.4 kB

  • Original 104.0 kB
  • After minification 89.6 kB
  • After compression 21.6 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. This page needs HTML code to be minified as it can gain 14.4 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 82.4 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 1.6 kB

  • Original 2.3 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. Sony images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 14.9 kB

  • Original 387.8 kB
  • After minification 381.9 kB
  • After compression 372.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

-28%

Potential reduce by 11.4 kB

  • Original 41.2 kB
  • After minification 38.8 kB
  • After compression 29.8 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 11.4 kB or 28% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (58%)

Requests Now

89

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 89 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 33 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

sony.co.jp

sony.co.jp

127 ms

sony.co.jp

sony.co.jp

19 ms

www.sony.co.jp

www.sony.co.jp

159 ms

TweenMax.min.js

TweenMax.min.js

48 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

276 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

210 ms

jquery.cookie.js

jquery.cookie.js

636 ms

includeCommon.js

includeCommon.js

1257 ms

tile.js

tile.js

556 ms

reset.css

reset.css

1464 ms

swiper.min.css

swiper.min.css

42 ms

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

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

70 ms

lib.js

lib.js

919 ms

common.js

common.js

1209 ms

search_resp_jp.css

search_resp_jp.css

1092 ms

jquery.min.js

jquery.min.js

69 ms

slick.min.js

slick.min.js

65 ms

picturefill.js

picturefill.js

40 ms

top3.js

top3.js

995 ms

sli2.js

sli2.js

1116 ms

slick.css

slick.css

68 ms

index3.css

index3.css

1322 ms

import.css

import.css

1330 ms

s_code.js

s_code.js

1332 ms

sc_ppv.js

sc_ppv.js

1886 ms

gtm.js

gtm.js

76 ms

mfx-serp.css

mfx-serp.css

14 ms

mfx-serp-resp.css

mfx-serp-resp.css

3 ms

mfx-sbox.js

mfx-sbox.js

4 ms

js

js

79 ms

js

js

75 ms

analytics.js

analytics.js

29 ms

collect

collect

255 ms

collect

collect

266 ms

collect

collect

260 ms

collect

collect

254 ms

collect

collect

37 ms

js

js

55 ms

js

js

108 ms

collect

collect

19 ms

js

js

107 ms

collect

collect

19 ms

js

js

108 ms

ga-audiences

ga-audiences

92 ms

font-awesome.css

font-awesome.css

6 ms

gtid

gtid

319 ms

P7XN4-V2TSB-2T8M6-FRSJA-ZK3CZ

P7XN4-V2TSB-2T8M6-FRSJA-ZK3CZ

156 ms

extsync

extsync

787 ms

logo.svg

logo.svg

1487 ms

slider_img-240322MV1_PC@2x.png

slider_img-240322MV1_PC@2x.png

1602 ms

slider_img-240426MV2_PC@2x.png

slider_img-240426MV2_PC@2x.png

1250 ms

slider_img-240422MV3_PC@2x.png

slider_img-240422MV3_PC@2x.png

1282 ms

slider_img-240418MV4_SP@2x.png

slider_img-240418MV4_SP@2x.png

146 ms

slider_img-240422MV5_PC@2x.png

slider_img-240422MV5_PC@2x.png

1642 ms

sli2_thum03.jpg

sli2_thum03.jpg

1115 ms

sli2_thum05.jpg

sli2_thum05.jpg

2050 ms

sli2_thum04.jpg

sli2_thum04.jpg

1845 ms

sli2_thum01.jpg

sli2_thum01.jpg

2611 ms

sli2_thum02.jpg

sli2_thum02.jpg

2316 ms

sli2_thum06.jpg

sli2_thum06.jpg

2246 ms

sli2_thum08.jpg

sli2_thum08.jpg

2560 ms

sli2_thum09.jpg

sli2_thum09.jpg

2644 ms

sli2_thum11.jpg

sli2_thum11.jpg

2705 ms

sli2_thum12.jpg

sli2_thum12.jpg

3032 ms

sli2_thum10.jpg

sli2_thum10.jpg

2890 ms

sli2_thum07.jpg

sli2_thum07.jpg

3240 ms

sli2_thum13.jpg

sli2_thum13.jpg

3365 ms

sli2_03_pc.jpg

sli2_03_pc.jpg

3452 ms

sli2_05_pc.jpg

sli2_05_pc.jpg

3496 ms

sli2_04_pc.jpg

sli2_04_pc.jpg

3694 ms

sli2_01_pc.jpg

sli2_01_pc.jpg

4189 ms

sli2_02_pc.jpg

sli2_02_pc.jpg

4338 ms

sli2_06_pc.jpg

sli2_06_pc.jpg

4179 ms

sli2_08_pc.jpg

sli2_08_pc.jpg

4064 ms

sli2_09_pc.jpg

sli2_09_pc.jpg

4391 ms

sli2_11_pc.jpg

sli2_11_pc.jpg

4270 ms

sli2_12_pc.jpg

sli2_12_pc.jpg

4077 ms

sli2_10_pc.jpg

sli2_10_pc.jpg

4190 ms

sli2_07_pc.jpg

sli2_07_pc.jpg

4206 ms

sli2_13_pc.jpg

sli2_13_pc.jpg

4208 ms

ico-info@2x.png

ico-info@2x.png

4221 ms

tmpl_footer_grouplink.png

tmpl_footer_grouplink.png

4217 ms

df549e883e793380_4254.js

df549e883e793380_4254.js

94 ms

slider_img-240418MV4_PC@2x.png

slider_img-240418MV4_PC@2x.png

5354 ms

config.json

config.json

64 ms

tracking.min.js

tracking.min.js

11 ms

td.min.js

td.min.js

35 ms

dd

dd

235 ms

s98773460206575

s98773460206575

7 ms

get_cookie_id

get_cookie_id

65 ms

td_accesslog

td_accesslog

18 ms

rep

rep

166 ms

Accessibility Review

sony.co.jp accessibility score

91

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

Tables and lists

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

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

85

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 doesn't use 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: