5.6 sec in total
893 ms
4.5 sec
246 ms
Welcome to pureson.co.jp homepage info - get ready to check Pureson best content right away, or after learning these important things about pureson.co.jp
洗剤OEM・除菌水OEM・消臭剤OEM・新型コロナウイルス等のウイルス対策のことなら国内トップクラス企業の株式会社ピュアソン。大手企業向けオリジナル製品開発、OEM実績多数。
Visit pureson.co.jpWe analyzed Pureson.co.jp page load time and found that the first response time was 893 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
pureson.co.jp performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value28.0 s
0/100
25%
Value12.4 s
3/100
10%
Value210 ms
88/100
30%
Value0.589
11/100
15%
Value16.7 s
5/100
10%
893 ms
324 ms
522 ms
553 ms
596 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 97% of them (66 requests) were addressed to the original Pureson.co.jp, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Pureson.co.jp.
Page size can be reduced by 61.6 kB (7%)
844.9 kB
783.3 kB
In fact, the total size of Pureson.co.jp main page is 844.9 kB. 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 754.9 kB which makes up the majority of the site volume.
Potential reduce by 8.1 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 8.1 kB or 67% of the original size.
Potential reduce by 4.2 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. Pureson images are well optimized though.
Potential reduce by 26.3 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 26.3 kB or 53% of the original size.
Potential reduce by 23.1 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. Pureson.co.jp needs all CSS files to be minified and compressed as it can save up to 23.1 kB or 82% of the original size.
Number of requests can be reduced by 18 (27%)
67
49
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pureson. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
pureson.co.jp
893 ms
import.css
324 ms
iepngfix.js
522 ms
rollover.js
553 ms
scrollsmoothly.js
596 ms
swfobject_modified.js
1010 ms
common.css
323 ms
module.css
192 ms
style.css
538 ms
elements.css
581 ms
news_s.php
188 ms
bg_header.gif
204 ms
logo.gif
324 ms
gnav_home_off.gif
194 ms
gnav_corporate_off.gif
192 ms
gnav_washing_off.gif
397 ms
gnav_effective_off.gif
348 ms
gnav_oem_off.gif
349 ms
gnav_inquiry_off.gif
369 ms
visualbk.png
403 ms
bg_illust01.gif
1132 ms
ban_pickup.png
521 ms
ban_food_off.png
1041 ms
ban_spa_off.png
1287 ms
ban_carmainte_off.png
1385 ms
ban_carfactory_off.png
1008 ms
bg_box_blue_w920m.gif
693 ms
bg_box_blue_w920b.gif
867 ms
bg_box_blue_w920t.jpg
1908 ms
entry_posture.png
1211 ms
entry_news.gif
1213 ms
entry_topics.jpg
1291 ms
ban_use_off.jpg
1414 ms
ban_oem_off.png
1560 ms
bg_box_green_w920m.gif
1471 ms
bg_box_green_w920b.gif
1451 ms
bg_box_green_w920t.jpg
1583 ms
entry_item.jpg
1615 ms
img_item_08.jpg
1613 ms
img_item_10.jpg
1653 ms
img_item_07.jpg
1734 ms
img_item_01.jpg
1782 ms
img_item_02.jpg
1774 ms
img_item_06.jpg
1816 ms
img_item_05.jpg
1837 ms
ga.js
8 ms
img_item_04.jpg
1879 ms
__utm.gif
13 ms
img_item_03.jpg
1751 ms
img_item_09.jpg
1794 ms
btn_pagetop.gif
1834 ms
bg_footer.gif
1827 ms
logo_info.jpg
1763 ms
icon_line.gif
1738 ms
txt_copy_01.png
1754 ms
txt_copy_02.png
1815 ms
gnav_home_on.gif
176 ms
gnav_corporate_on.gif
204 ms
gnav_washing_on.gif
164 ms
gnav_effective_on.gif
186 ms
gnav_oem_on.gif
176 ms
gnav_inquiry_on.gif
200 ms
ban_food_on.png
683 ms
ban_spa_on.png
519 ms
ban_carmainte_on.png
694 ms
ban_carfactory_on.png
736 ms
ban_use_on.jpg
397 ms
ban_oem_on.png
604 ms
pureson.co.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.
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 IDs are not unique
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 valid value for its [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
Links do not have a discernible name
pureson.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
pureson.co.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
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 Pureson.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 Pureson.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.
pureson.co.jp
Open Graph description is not detected on the main page of Pureson. 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: