7.2 sec in total
360 ms
6.4 sec
380 ms
Click here to check amazing REGZA content for Japan. Otherwise, check out these important facts you probably never knew about regza.jp
テレビ REGZA〈レグザ〉。「これが、リアルだ。視界が世界になる」ミリ波レーダー採用レグザセンシング搭載モデル誕生。タイムシフトマシン4K Mini LED液晶モデル、レグザ史上最高クラスの4K有機ELモデルが誕生!広色域量子ドット・倍速4K液晶、レコーダーなどの商品や楽しみ方をご紹介。
Visit regza.jpWe analyzed Regza.jp page load time and found that the first response time was 360 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
regza.jp performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value30.0 s
0/100
25%
Value21.1 s
0/100
10%
Value1,040 ms
26/100
30%
Value0.001
100/100
15%
Value22.5 s
1/100
10%
360 ms
1035 ms
642 ms
694 ms
553 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Regza.jp, 92% (89 requests) were made to Toshiba.co.jp and 4% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Toshiba.co.jp.
Page size can be reduced by 418.7 kB (17%)
2.5 MB
2.1 MB
In fact, the total size of Regza.jp main page is 2.5 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 2.0 MB which makes up the majority of the site volume.
Potential reduce by 37.8 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 37.8 kB or 78% of the original size.
Potential reduce by 69.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. REGZA images are well optimized though.
Potential reduce by 287.8 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 287.8 kB or 66% of the original size.
Potential reduce by 24.0 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. Regza.jp needs all CSS files to be minified and compressed as it can save up to 24.0 kB or 74% of the original size.
Number of requests can be reduced by 17 (18%)
94
77
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of REGZA. 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.
regza.jp
360 ms
1035 ms
base.css
642 ms
top.css
694 ms
modernizr.js
553 ms
jquery.js
677 ms
jquery.touchSwipe.js
274 ms
plugins.js
1742 ms
common.js
323 ms
top-min.js
339 ms
header.gif
176 ms
nav.gif
211 ms
logo_toshiba.gif
269 ms
identifier.gif
292 ms
bg.jpg
1726 ms
bg.jpg
2781 ms
bg.jpg
2504 ms
bg.jpg
2830 ms
bg.jpg
1301 ms
bg.jpg
2653 ms
controller.png
1686 ms
ttl_4k_regza.png
1850 ms
img_z20x.jpg
1900 ms
img_z10x.jpg
2010 ms
img_j20x.jpg
2075 ms
img_g20x.jpg
2173 ms
ttl_regza.png
2254 ms
img_v30.jpg
2335 ms
img_s10.jpg
2427 ms
img_s11.jpg
2497 ms
img_icon.png
2605 ms
txt_quality.png
2658 ms
chart_quality.png
2825 ms
txt_recording.png
2779 ms
chart_recording.png
2827 ms
txt_sound.png
2825 ms
chart_sound.png
2961 ms
txt_network.png
2953 ms
chart_network.png
2996 ms
txt_tuner.png
2984 ms
chart_tuner.png
2946 ms
btn_spec_list.png
2936 ms
ttl_regzasound.png
3027 ms
img_regzasound.jpg
3031 ms
ttl_regzausbhdd.png
2980 ms
img_regzausbhdd.jpg
2947 ms
ttl_portabletv.png
2905 ms
img_portable.jpg
2881 ms
ttl_lineup.png
2820 ms
img_size.png
2036 ms
ga.js
5 ms
nav_feature.png
1768 ms
inpage_linkid.js
40 ms
bi.js
385 ms
__utm.gif
11 ms
__utm.gif
3 ms
collect
59 ms
news.json
1632 ms
bnr_hull_01.jpg
2118 ms
bnr_large_11.jpg
1827 ms
bnr_large_03.jpg
1755 ms
328 ms
bnr_large_04.jpg
1636 ms
bnr_large_12.jpg
1727 ms
bnr_07.jpg
1531 ms
bnr_05.jpg
1555 ms
bnr_04.jpg
1667 ms
bnr_large_13.jpg
1590 ms
bnr_large_10.jpg
1760 ms
bnr_large_01.jpg
1464 ms
ttl_guide.png
1364 ms
bnr_12.jpg
1361 ms
bnr_11.jpg
1470 ms
bnr_10.jpg
1357 ms
bnr_07.jpg
1398 ms
bnr_06.jpg
1357 ms
bnr_05.jpg
1362 ms
bnr_03.jpg
1465 ms
bnr_02.jpg
1468 ms
controller.png
1402 ms
logo_timeshift.png
1392 ms
logo_regza_link.png
1372 ms
logo_timeon.png
1457 ms
logo_apps.png
1458 ms
ttl_news.gif
1461 ms
btn_news_list.gif
1395 ms
btn_rss.gif
1381 ms
icon.png
1380 ms
img_eftc.png
1479 ms
btn_pagetop.png
1446 ms
img_other.png
1450 ms
txt_sitemap.png
1391 ms
bnr_photo.jpg
1387 ms
bnr_canvio.jpg
1388 ms
bnr_room1048.gif
1442 ms
bnr_tdirect.gif
1139 ms
copyright.gif
1164 ms
regza.jp 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-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
regza.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
regza.jp 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
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Regza.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 Regza.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.
regza.jp
Open Graph data is detected on the main page of REGZA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: