5.7 sec in total
830 ms
4.6 sec
267 ms
Visit 003003.jp now to see the best up-to-date 003003 content for Japan and also check out these interesting facts you probably never knew about 003003.jp
10年かけて開発されたおいしい青汁の青汁専門会社、アサヒ緑健の【公式サイト】。手軽に毎日飲み続けたくなる”こだわりのおいしさ”と”豊富な栄養”をご家庭で。有機JAS認証栽培された青汁専用の大麦若葉『麦王』使用。
Visit 003003.jpWe analyzed 003003.jp page load time and found that the first response time was 830 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
003003.jp performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value10.1 s
0/100
25%
Value14.0 s
1/100
10%
Value16,860 ms
0/100
30%
Value1
2/100
15%
Value26.0 s
0/100
10%
830 ms
518 ms
547 ms
562 ms
413 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 23% of them (14 requests) were addressed to the original 003003.jp, 70% (42 requests) were made to Cdn.0120003003.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Cdn.0120003003.com.
Page size can be reduced by 206.2 kB (12%)
1.7 MB
1.5 MB
In fact, the total size of 003003.jp main page is 1.7 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 15.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 3.7 kB, which is 18% 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 15.6 kB or 77% of the original size.
Potential reduce by 70.4 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. 003003 images are well optimized though.
Potential reduce by 100.7 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 100.7 kB or 64% of the original size.
Potential reduce by 19.7 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. 003003.jp needs all CSS files to be minified and compressed as it can save up to 19.7 kB or 83% of the original size.
Number of requests can be reduced by 13 (22%)
59
46
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 003003. 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 5 to 1 for CSS and as a result speed up the page load time.
003003.jp
830 ms
5_base.css
518 ms
5_indexpage.css
547 ms
font-medium.css
562 ms
header_copy.png
413 ms
header_tel.png
602 ms
top_main_img_08.png
1486 ms
top_main_img_07.png
1153 ms
top_main_img_01.jpg
682 ms
top_main_img_04.jpg
855 ms
top_itemA01.png
1055 ms
top_itemA04.png
1207 ms
top_itemA06.png
1159 ms
top_itemA03.png
1515 ms
top_itemA02.png
1531 ms
top_button_gototop.png
1500 ms
banner_06.gif
1487 ms
banner_07.gif
1593 ms
banner_04.gif
1808 ms
banner_01.png
1982 ms
banner_08.png
1825 ms
footer_logo.png
1852 ms
footer_tel.png
2150 ms
footer_time.png
1778 ms
footer_address.png
1984 ms
footer_button_info.png
1990 ms
footer_button_top.png
2011 ms
getseal
82 ms
cp.js
433 ms
logo_pmark.png
1963 ms
logo_jdma.png
2280 ms
sps.js
480 ms
jquery-1.10.2.min.js
1228 ms
easySlider1.7.js
545 ms
styleswitcher.js
670 ms
google-analytics.js
684 ms
index.js
689 ms
open.js
900 ms
getseal
94 ms
header_logo.png
1845 ms
header_button_02.png
1861 ms
header_button_03.png
1888 ms
header_button_05.png
1895 ms
header_button_04.png
2007 ms
menu_button_01.png
2056 ms
menu_button_02.png
2051 ms
menu_button_03.png
2253 ms
menu_button_04.png
2231 ms
menu_button_05.png
2252 ms
menu_button_06.png
2374 ms
top_cont_ban_mugioh.png
3344 ms
top_cont_ban_kodawari.png
2533 ms
newsrelease_li.png
2473 ms
top_content_long.png
2301 ms
analytics.js
49 ms
top_arrow_right.png
1540 ms
top_arrow_left.png
1843 ms
font-small.css
273 ms
collect
12 ms
font-large.css
186 ms
003003.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-hidden="true"] elements contain focusable descendents
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
003003.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
Browser errors were logged to the console
Page has valid source maps
003003.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 003003.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 003003.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.
003003.jp
Open Graph description is not detected on the main page of 003003. 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: