6.4 sec in total
630 ms
5.4 sec
351 ms
Welcome to vaio.com homepage info - get ready to check VAIO best content for Japan right away, or after learning these important things about vaio.com
重要なお知らせ Type-C標準ACアダプター(VJ8PD65W)予防交換のお願い 個人向け標準仕様モデルカタ
Visit vaio.comWe analyzed Vaio.com page load time and found that the first response time was 630 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
vaio.com performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value14.3 s
0/100
25%
Value10.0 s
9/100
10%
Value2,000 ms
8/100
30%
Value0.024
100/100
15%
Value14.3 s
9/100
10%
630 ms
494 ms
320 ms
795 ms
322 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 72% of them (46 requests) were addressed to the original Vaio.com, 6% (4 requests) were made to Google-analytics.com and 5% (3 requests) were made to Fast.fonts.net. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Vaio.com.
Page size can be reduced by 592.7 kB (16%)
3.8 MB
3.2 MB
In fact, the total size of Vaio.com main page is 3.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. 30% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 22.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 4.5 kB, which is 15% 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 22.6 kB or 75% of the original size.
Potential reduce by 285.1 kB
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. VAIO images are well optimized though.
Potential reduce by 164.6 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 164.6 kB or 70% of the original size.
Potential reduce by 120.4 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. Vaio.com needs all CSS files to be minified and compressed as it can save up to 120.4 kB or 91% of the original size.
Number of requests can be reduced by 16 (27%)
59
43
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of VAIO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
vaio.com
630 ms
styles_2.css
494 ms
top.css
320 ms
jquery.min.js
795 ms
jquery.easing.min.js
322 ms
top.js
337 ms
ct17007.js
507 ms
1fc04cdc-51a8-4215-a671-f3bda2cc8853.css
132 ms
analytics.js
79 ms
logo.png
180 ms
main-logo-2.png
181 ms
main-logo-1.png
183 ms
pic-main-kai.jpg
1282 ms
pic-main-biz.jpg
994 ms
pic-main-z.jpg
4070 ms
pic-main-s13.jpg
1134 ms
pic-main-s15.jpg
1553 ms
pic-main-s11.jpg
1586 ms
pic-main-z_canvas.jpg
1825 ms
main-txt-z_canvas.png
1326 ms
btn-win10-support.png
1441 ms
pic-product_z_mini.jpg
1522 ms
img_new.png
1604 ms
bg-arrow2.png
1690 ms
pic-product_z_canvas_mini.jpg
1717 ms
pic-product_s11.jpg
1747 ms
pic-product_s13.jpg
1763 ms
pic-product_s15.jpg
1882 ms
pic-product_vaio_phone_biz.jpg
1880 ms
pic-product_pro_mk2_mini.jpg
1913 ms
pic-product_fit_mk2_mini.jpg
1925 ms
img_specialmovie.jpg
2979 ms
img_kachiiro.jpg
2364 ms
btn-down.png
2040 ms
btn-up.png
2073 ms
pick-m-20160202.jpg
2085 ms
pic-qualitytest_pro_mini.jpg
2200 ms
pic-m-20160128.jpg
2242 ms
pic-m-20151222.png
2251 ms
pic-sim.png
2366 ms
pic-recruit_mini.png
2462 ms
pic-business_solution_mini.png
2465 ms
pic-topics3_mini.png
2524 ms
icon.png
2536 ms
ico_fb.png
2559 ms
Trace
582 ms
24150016
321 ms
c5a7f89e-15b6-49a9-8259-5ea665e72191.woff
29 ms
4bf0ead4-e61b-4992-832b-6ff05828d99f.woff
75 ms
linkid.js
12 ms
collect
16 ms
collect
81 ms
ico_tw.png
2449 ms
ico_yt.png
2506 ms
btn-close.png
2519 ms
ecotag.php
711 ms
tr
44 ms
collect
18 ms
18 ms
lb
62 ms
s_retargeting.js
585 ms
17 ms
18 ms
18 ms
vaio.com accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
vaio.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
vaio.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vaio.com 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 Vaio.com 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.
vaio.com
Open Graph data is detected on the main page of VAIO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: