5.9 sec in total
1 sec
4.6 sec
192 ms
Welcome to purefood.co.jp homepage info - get ready to check Purefood best content for Japan right away, or after learning these important things about purefood.co.jp
食肉加工と畜産エキス加工の事業を強みとし、お客様のニーズに細かくお応えする商品をお届けします。
Visit purefood.co.jpWe analyzed Purefood.co.jp page load time and found that the first response time was 1 sec 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.
purefood.co.jp performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value12.5 s
0/100
25%
Value7.6 s
25/100
10%
Value120 ms
97/100
30%
Value0.001
100/100
15%
Value5.3 s
73/100
10%
1012 ms
296 ms
485 ms
512 ms
537 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 95% of them (52 requests) were addressed to the original Purefood.co.jp, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Purefood.co.jp.
Page size can be reduced by 210.3 kB (20%)
1.1 MB
857.1 kB
In fact, the total size of Purefood.co.jp main page is 1.1 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. 20% of websites need less resources to load. Images take 784.7 kB which makes up the majority of the site volume.
Potential reduce by 14.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 14.1 kB or 76% of the original size.
Potential reduce by 42.3 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. Purefood images are well optimized though.
Potential reduce by 137.4 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 137.4 kB or 56% of the original size.
Potential reduce by 16.5 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. Purefood.co.jp needs all CSS files to be minified and compressed as it can save up to 16.5 kB or 82% of the original size.
Number of requests can be reduced by 16 (30%)
54
38
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Purefood. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
purefood.co.jp
1012 ms
reset.css
296 ms
common.css
485 ms
top.css
512 ms
slick-top.css
537 ms
lg_pf_2014.png
376 ms
lg_header_umai.png
443 ms
bt_i_side_message.png
579 ms
bt_p_side_menu.png
591 ms
spacer.gif
396 ms
ic_i_cp_bg.png
454 ms
ic_i_cp.png
828 ms
ic_i_ca_150911.png
699 ms
lg_staminaen.png
1222 ms
lg_nabe.png
594 ms
bt_i_q_hover_1.png
689 ms
bt_i_q_hover_2.png
616 ms
bt_i_a_hover_1.png
793 ms
bt_i_a_hover_2.png
781 ms
bt_i_r_hover_1.png
835 ms
jquery.min.js
32 ms
heightLine.js
877 ms
jquery.Pc2Sp.js
941 ms
logo2_edgePreload.js
988 ms
jquery.cycle2.min.js
997 ms
bt_i_r_hover_2.png
980 ms
bt_i_r_hover_3.png
1059 ms
bt_i_pc_hover_1.png
1102 ms
bt_i_pc_hover_2.png
1128 ms
bt_contact.png
1187 ms
lg_nh_2014.png
1167 ms
jQueryRotateCompressed.js
1047 ms
slick.min.js
1077 ms
im_i_sl_sta_2016.jpg
2717 ms
im_i_sl_salsiccia_2016.jpg
2176 ms
im_i_sl_torigara_2015.jpg
2016 ms
im_i_sl_umai.jpg
3337 ms
bt_gn_home.png
1061 ms
bt_gn_product.png
1071 ms
bt_gn_quality.png
1241 ms
bt_gn_about.png
1235 ms
bt_gn_recruit.png
1399 ms
bt_gn_pureclub.png
1420 ms
cp_footer_copyright.png
1544 ms
edge.2.0.1.min.js
2223 ms
logo2_edge.js
1092 ms
logo2_edgeActions.js
1255 ms
ga.js
6 ms
__utm.gif
12 ms
bt_slider_l.png
1064 ms
bt_slider_r.png
1229 ms
ajax-loader.gif
1227 ms
edge.2.0.1.min.js
1301 ms
logo2_edge.js
199 ms
logo2_edgeActions.js
201 ms
purefood.co.jp accessibility score
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.
purefood.co.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
General
Impact
Issue
Detected JavaScript libraries
purefood.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
Links do not have descriptive text
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 Purefood.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 Purefood.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.
purefood.co.jp
Open Graph description is not detected on the main page of Purefood. 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: