4.3 sec in total
935 ms
3.2 sec
215 ms
Visit homepage-produce.com now to see the best up-to-date Homepage Produce content and also check out these interesting facts you probably never knew about homepage-produce.com
様々な事業立ち上げの経験を基に、Webプロデューサーとして、またWeb関連の講師として活動する筆者が見てきた中小企業の犯しやすい失敗するホームページ制作事例を紹介します。
Visit homepage-produce.comWe analyzed Homepage-produce.com page load time and found that the first response time was 935 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
homepage-produce.com performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value2.8 s
82/100
25%
Value4.9 s
66/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.8 s
97/100
10%
935 ms
498 ms
347 ms
354 ms
1088 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 91% of them (51 requests) were addressed to the original Homepage-produce.com, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Js.addclips.org. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Homepage-produce.com.
Page size can be reduced by 147.8 kB (33%)
448.1 kB
300.3 kB
In fact, the total size of Homepage-produce.com main page is 448.1 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. 25% of websites need less resources to load. Images take 251.1 kB which makes up the majority of the site volume.
Potential reduce by 15.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 15.7 kB or 71% of the original size.
Potential reduce by 0 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. Homepage Produce images are well optimized though.
Potential reduce by 119.6 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 119.6 kB or 75% of the original size.
Potential reduce by 12.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. Homepage-produce.com needs all CSS files to be minified and compressed as it can save up to 12.5 kB or 80% of the original size.
Number of requests can be reduced by 28 (51%)
55
27
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Homepage Produce. 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 4 to 1 for CSS and as a result speed up the page load time.
homepage-produce.com
935 ms
index.css
498 ms
SpryValidationTextField.css
347 ms
SpryValidationTextarea.css
354 ms
SpryValidationTextField.js
1088 ms
SpryValidationTextarea.js
937 ms
index.js
689 ms
addclips.js
720 ms
bodyBack.jpg
183 ms
wrapperBackB.jpg
184 ms
headerBack.jpg
166 ms
h1B.jpg
530 ms
h2B.jpg
189 ms
header.jpg
346 ms
contentsBack.jpg
331 ms
centerBack.jpg
364 ms
centerBoxBack.jpg
364 ms
topH2a.jpg
376 ms
centerP.jpg
496 ms
centerPBottom.jpg
518 ms
topH2b.jpg
545 ms
centerBottom.jpg
546 ms
topNextButton.jpg
563 ms
subH2NewB.jpg
659 ms
fH2a.jpg
690 ms
check.jpg
703 ms
fH2b.jpg
725 ms
fH2c.jpg
729 ms
fH2d.jpg
750 ms
fH2e.jpg
823 ms
fH2f.jpg
863 ms
menuBack.jpg
879 ms
menuH2.jpg
907 ms
menuH3a.jpg
908 ms
menuLink.jpg
937 ms
menuH3b.jpg
988 ms
menuH3c.jpg
1034 ms
menuH3d.jpg
1054 ms
menuH3e.jpg
1087 ms
menuH3f.jpg
1090 ms
menuBottom.jpg
1123 ms
itemClose.jpg
1152 ms
footer.jpg
1206 ms
addclips.css
373 ms
addclips_2.gif
354 ms
fontBack.jpg
1154 ms
fontL.jpg
1110 ms
fontM.jpg
1097 ms
fontS.jpg
1135 ms
pageH2.jpg
1136 ms
pageTop.jpg
1057 ms
pageBack.jpg
1068 ms
pageIcon.jpg
1094 ms
rssIcon.gif
1097 ms
ga.js
5 ms
__utm.gif
13 ms
homepage-produce.com accessibility score
homepage-produce.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
homepage-produce.com SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Homepage-produce.com 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 Homepage-produce.com 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.
homepage-produce.com
Open Graph description is not detected on the main page of Homepage Produce. 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: