11.2 sec in total
1.8 sec
6.2 sec
3.2 sec
Welcome to engei.net homepage info - get ready to check Engei best content for Japan right away, or after learning these important things about engei.net
『園芸ネット』は植物とガーデニングの通販サイト。花や観葉植物、野菜、ハーブの種苗から園芸用品まで豊富な品揃え。
Visit engei.netWe analyzed Engei.net page load time and found that the first response time was 1.8 sec and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
engei.net performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value11.8 s
0/100
25%
Value10.2 s
8/100
10%
Value550 ms
54/100
30%
Value0.296
40/100
15%
Value10.1 s
26/100
10%
1798 ms
1108 ms
28 ms
386 ms
378 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 23% of them (24 requests) were addressed to the original Engei.net, 66% (70 requests) were made to Cdn.engei.net and 4% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Cdn.engei.net.
Page size can be reduced by 667.7 kB (12%)
5.4 MB
4.7 MB
In fact, the total size of Engei.net main page is 5.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.8 MB which makes up the majority of the site volume.
Potential reduce by 294.3 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 294.3 kB or 82% of the original size.
Potential reduce by 154.6 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. Engei images are well optimized though.
Potential reduce by 127.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 127.4 kB or 64% of the original size.
Potential reduce by 91.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. Engei.net needs all CSS files to be minified and compressed as it can save up to 91.3 kB or 98% of the original size.
Number of requests can be reduced by 20 (19%)
104
84
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Engei. 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 8 to 1 for CSS and as a result speed up the page load time.
engei.net
1798 ms
notsmart.css
1108 ms
jquery.min.js
28 ms
validationEngine.jquery.css
386 ms
superfish.css
378 ms
superfish-vertical.css
400 ms
scrolltopcontrol.js
292 ms
ga.js
99 ms
gentei.jpg
201 ms
1season_auricula.jpg
499 ms
flower_3.jpgy.jpg
484 ms
spring-tree2015.jpg
501 ms
frenchseed.jpg
471 ms
dahlia.jpg
492 ms
link_briers620.jpg
483 ms
brand_WOLF_Garten.jpg
1027 ms
030063i2.jpg
1014 ms
95850.jpg
1018 ms
24201.jpg
1041 ms
117746.jpg
1040 ms
67450.jpg
1037 ms
73976.jpg
2233 ms
1942.jpg
2219 ms
89956.jpg
2228 ms
90211.jpg
2256 ms
61282.jpg
2221 ms
12550.jpg
1146 ms
117880.jpg
2256 ms
119172.jpg
2273 ms
77988.jpg
2278 ms
119244.jpg
2280 ms
118726.jpg
2302 ms
54674.jpg
2300 ms
118626.jpg
2310 ms
118618.jpg
2336 ms
117648i1.jpg
2328 ms
114747.jpg
2344 ms
41161.jpg
2346 ms
52840.jpg
2351 ms
87743.jpg
2444 ms
114079.jpg
2468 ms
76455.jpg
2446 ms
93620.jpg
2474 ms
M_116190.jpg
2477 ms
bg_head.jpg
191 ms
sprite.png
2313 ms
t.gif
208 ms
logo.png
202 ms
link_kaboku_270.jpg
584 ms
engeijs.js
274 ms
jquery.innerfade.js
324 ms
jqueryAutoHeight.js
331 ms
hoverIntent.js
367 ms
superfish.js
389 ms
jquery.validationEngine.js
482 ms
jquery.validationEngine-ja.js
509 ms
jquery.bxslider.js
983 ms
jquery.bxslider.css
570 ms
twitter.html
406 ms
__utm.gif
22 ms
archinet.jpg
444 ms
link_022093_270.jpg
855 ms
M_116242.jpg
2291 ms
collect
58 ms
M_116047.jpg
2236 ms
M_116219.jpg
2473 ms
widgets.js
14 ms
M_114767.jpg
2181 ms
M_108038.jpg
2179 ms
M_15575.jpg
2175 ms
M_85322.jpg
2454 ms
timeline.fe2df323b0284f547735e29f610f34bf.js
20 ms
syndication
104 ms
344612443915419648
188 ms
timeline.d6812d7a233cc6acdaf452b485c20172.default.css
5 ms
timeline.d6812d7a233cc6acdaf452b485c20172.default.css
9 ms
engeitwitter_normal.jpg
209 ms
M_19982.jpg
1992 ms
M_58786.jpg
1993 ms
M_75549.jpg
1986 ms
M_85275.jpg
2009 ms
M_103714.jpg
2169 ms
M_18316.jpg
2179 ms
M_100861.jpg
1191 ms
link_1season_paccot.jpg
1202 ms
link_sakura270.jpg
1187 ms
kotori.jpg
1218 ms
tsubaki_banner.jpg
1347 ms
link_030092_270.jpg
1358 ms
link_kinenju270.jpg
1524 ms
link_herbyouto270.jpg
1533 ms
link_olive270.jpg
1522 ms
link_023150_270.jpg
1353 ms
link_yoridori270.jpg
1687 ms
link_bluegarden_270.jpg
1689 ms
link_pinkgarden_270.jpg
1716 ms
print.css
318 ms
link_yellowgarden_270.jpg
1843 ms
link_redgarden_270.jpg
1843 ms
link_whitegarden_270.jpg
1863 ms
link_huiri270.jpg
2047 ms
credit2p3.jpg
1951 ms
up.png
2039 ms
bx_loader.gif
1903 ms
controls.png
2097 ms
jot
30 ms
engei.net 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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
engei.net 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
engei.net 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
Tap targets are not sized appropriately
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Engei.net 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 Engei.net main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
engei.net
Open Graph description is not detected on the main page of Engei. 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: