6.5 sec in total
616 ms
5.5 sec
417 ms
Visit honestbee.jp now to see the best up-to-date Honestbee content for Japan and also check out these interesting facts you probably never knew about honestbee.jp
コストコ会員歴21年・元店員3年のコストコブロガーもち子が、3,000商品超の実食レビューと最新セール・新商品・値段情報をわかりやすく解説してます。買い物前に読むと役立つコストコ情報ブログです。
Visit honestbee.jpWe analyzed Honestbee.jp page load time and found that the first response time was 616 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
honestbee.jp performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value7.3 s
4/100
25%
Value9.7 s
11/100
10%
Value660 ms
45/100
30%
Value0.001
100/100
15%
Value14.3 s
9/100
10%
616 ms
717 ms
1453 ms
54 ms
201 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Honestbee.jp, 83% (48 requests) were made to Hubmedia.co.jp and 3% (2 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Hubmedia.co.jp.
Page size can be reduced by 167.8 kB (20%)
821.3 kB
653.5 kB
In fact, the total size of Honestbee.jp main page is 821.3 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. 45% of websites need less resources to load. Javascripts take 373.9 kB which makes up the majority of the site volume.
Potential reduce by 71.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. 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 71.7 kB or 79% of the original size.
Potential reduce by 10 B
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. Honestbee images are well optimized though.
Potential reduce by 47.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 47.8 kB or 13% of the original size.
Potential reduce by 48.3 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. Honestbee.jp needs all CSS files to be minified and compressed as it can save up to 48.3 kB or 40% of the original size.
Number of requests can be reduced by 31 (57%)
54
23
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Honestbee. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
{{url}}
{{time}} ms
honestbee.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
[id] attributes on active, focusable elements are not unique
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
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.
honestbee.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
honestbee.jp SEO score
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 Honestbee.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 Honestbee.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.
{{og_description}}
honestbee.jp
Open Graph description is not detected on the main page of Honestbee. 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: