Tools & Wizards About Us

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

sonymobile.jp

Xperia（エクスペリア）ホーム | Xperia（エクスペリア）公式サイト

Page Load Speed

6.4 sec in total

First Response

22 ms

Resources Loaded

5.7 sec

Page Rendered

705 ms

About Website

Visit sonymobile.jp now to see the best up-to-date Sonymobile content for Japan and also check out these interesting facts you probably never knew about sonymobile.jp

Xperia（エクスペリア）公式サイトのホームです。ソニーのスマホ Xperiaの製品情報（仕様、デザイン、ディスプレイ、カメラ、オーディオなど）。Xperiaの機 能を詳しく解説する使いこなしガイド、こだわりで選べる約3,500アイテムの豊富なスマホカバー、スマホケースの紹介。お得なキャンペーンやイベントなどの最新情報。Android（アンドロイド）のバージョンアップ情報やサポート、会社情報、採...

Visit sonymobile.jp

Key Findings

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

Performance Metrics

sonymobile.jp performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value27.3 s

0/100

25%

SI (Speed Index)

Value22.1 s

0/100

10%

TBT (Total Blocking Time)

Value8,230 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value71.9 s

0/100

10%

Network Requests Diagram

sonymobile.jp

22 ms

xperia.sony.jp

626 ms

202 ms

style.css

690 ms

common-lib.min.js

666 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Sonymobile.jp, 92% (56 requests) were made to Sony.jp and 3% (2 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Sony.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (20%)

Content Size

7.1 MB

After Optimization

5.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sonymobile.jp main page is 7.1 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 4.6 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 38.2 kB

  • Original 47.4 kB
  • After minification 37.6 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 9.7 kB, which is 21% 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 38.2 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 53.8 kB

  • Original 4.6 MB
  • After minification 4.5 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. Sonymobile images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 1.3 MB

  • Original 2.1 MB
  • After minification 2.1 MB
  • After compression 807.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 1.3 MB or 62% of the original size.

CSS Optimization

-2%

Potential reduce by 9.0 kB

  • Original 421.8 kB
  • After minification 421.8 kB
  • After compression 412.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. Sonymobile.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 26 (46%)

Requests Now

57

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

sonymobile.jp accessibility score

66

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

High

[aria-*] attributes do not have valid values

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

Buttons do not have an accessible name

High

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

High

Image elements do not have [alt] attributes

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.

Best Practices

sonymobile.jp best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

sonymobile.jp SEO score

75

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Sonymobile.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 Sonymobile.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

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