24.3 sec in total
456 ms
935 ms
22.9 sec
Welcome to puredigital.jp homepage info - get ready to check Pure Digital best content for Japan right away, or after learning these important things about puredigital.jp
デジタルオーディオ、ホーンスピーカー、真空管アンプによるピュアオーディオシステム
Visit puredigital.jpWe analyzed Puredigital.jp page load time and found that the first response time was 456 ms and then it took 23.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
puredigital.jp performance score
name
value
score
weighting
Value1.8 s
90/100
10%
Value2.8 s
84/100
25%
Value2.1 s
99/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.9 s
99/100
10%
456 ms
25 ms
21 ms
31 ms
33 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Puredigital.jp, 81% (68 requests) were made to Blog-imgs-88.fc2.com and 8% (7 requests) were made to Counter1-cdn.fc2.com. The less responsive or slowest element that took the longest time to load (490 ms) relates to the external source Blog-imgs-88.fc2.com.
Page size can be reduced by 219.6 kB (2%)
13.8 MB
13.6 MB
In fact, the total size of Puredigital.jp main page is 13.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. 85% 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 13.6 MB which makes up the majority of the site volume.
Potential reduce by 165.7 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 58.2 kB, which is 29% 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 165.7 kB or 83% of the original size.
Potential reduce by 42.5 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. Pure Digital images are well optimized though.
Potential reduce by 3.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 3.9 kB or 74% of the original size.
Potential reduce by 7.6 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. Puredigital.jp needs all CSS files to be minified and compressed as it can save up to 7.6 kB or 76% of the original size.
Number of requests can be reduced by 5 (6%)
83
78
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pure Digital. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
puredigital.jp
456 ms
ba667.css
25 ms
120710style.css
21 ms
20160308124104607.jpg
31 ms
20160308124119917.jpg
33 ms
20160306190255205.jpg
31 ms
20160305164753686.jpg
29 ms
20160305181825633.jpg
42 ms
20160229221218160.jpg
96 ms
20160228232412306.jpg
31 ms
20160226172814482.jpg
31 ms
20160226172649868.jpg
56 ms
toridal-PS3.gif
236 ms
non-PS3.gif
33 ms
reg-PS3.gif
64 ms
CB-PS3.gif
66 ms
CBS-PS3.gif
42 ms
L-PS3.gif
63 ms
S-PS3.gif
64 ms
non-PS.gif
93 ms
switching-PS2.gif
94 ms
reg-PS2.gif
89 ms
20160214155815789.jpg
88 ms
20160214155853412.jpg
90 ms
20160214224751225.jpg
98 ms
20160213224047571.jpg
127 ms
20160213224136572.jpg
110 ms
20160211191111247.jpg
108 ms
20160211171407293.jpg
112 ms
20160211171435167.jpg
100 ms
HSO-14.jpg
139 ms
20160209231911179.jpg
169 ms
block80.gif
113 ms
20160207163802643.jpg
136 ms
20160206213524711.jpg
139 ms
sh_fc2blogheadbar_logo.png
16 ms
back.gif
16 ms
body_back.gif
7 ms
system131208s.jpg
15 ms
20160204193454715.jpg
63 ms
20160203205529459.jpg
117 ms
20160201190956386.jpg
118 ms
20160201195200279.jpg
86 ms
20160131142337604.jpg
76 ms
20160130195634632.jpg
88 ms
20160130185015400.jpg
92 ms
20160130155814536.jpg
92 ms
20160130155735747.jpg
107 ms
20160130155859588.jpg
99 ms
SWD-CL10-1.jpg
294 ms
SWD-CL10-2.jpg
309 ms
SWD-CL10-3.jpg
313 ms
20160129230339395.jpg
117 ms
MV89A.jpg
372 ms
swd-cl10.jpg
133 ms
20160126222933a7d.gif
278 ms
digital-part.jpg
297 ms
block77.gif
278 ms
20151115010222b88.gif
281 ms
201601232346040dd.gif
295 ms
D-70up2.jpg
297 ms
D-70.jpg
296 ms
20160110140838876.gif
293 ms
2016011014090684b.gif
289 ms
201512270021589cb.gif
285 ms
counter.php
262 ms
20160106000850272.jpg
280 ms
2016010115393645a.gif
286 ms
20160103131732995.jpg
278 ms
20160103130732778.jpg
285 ms
20160102174037661.jpg
275 ms
20151230174157056.jpg
490 ms
block76.gif
284 ms
motu828X-2.jpg
274 ms
multi2.gif
259 ms
315fc17d.jpg
32 ms
counter_js.php
97 ms
l.gif
28 ms
3.gif
24 ms
6.gif
13 ms
5.gif
13 ms
8.gif
13 ms
1.gif
15 ms
r.gif
14 ms
puredigital.jp accessibility score
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
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.
puredigital.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
puredigital.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Puredigital.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Puredigital.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.
puredigital.jp
Open Graph data is detected on the main page of Pure Digital. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: