9.4 sec in total
1.3 sec
7.6 sec
450 ms
Visit greencare.com.my now to see the best up-to-date Greencare content and also check out these interesting facts you probably never knew about greencare.com.my
Greencare Services Sdn. Bhd. was established in 2010 in Malaysia. The company was formed to service a number of markets in the turf and lawn care by formulating a wide range of commodity and specialty...
Visit greencare.com.myWe analyzed Greencare.com.my page load time and found that the first response time was 1.3 sec and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
greencare.com.my performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value6.1 s
12/100
25%
Value8.6 s
17/100
10%
Value290 ms
80/100
30%
Value0.207
60/100
15%
Value7.1 s
52/100
10%
1339 ms
258 ms
495 ms
906 ms
686 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 76% of them (64 requests) were addressed to the original Greencare.com.my, 18% (15 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Greencare.com.my.
Page size can be reduced by 59.0 kB (1%)
8.1 MB
8.1 MB
In fact, the total size of Greencare.com.my main page is 8.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. 50% of websites need less resources to load. Images take 7.8 MB which makes up the majority of the site volume.
Potential reduce by 41.5 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 41.5 kB or 82% of the original size.
Potential reduce by 2.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. Greencare images are well optimized though.
Potential reduce by 7.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. This website has mostly compressed JavaScripts.
Potential reduce by 7.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. Greencare.com.my has all CSS files already compressed.
Number of requests can be reduced by 37 (59%)
63
26
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greencare. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
greencare.com.my
1339 ms
font-awesome.min.css
258 ms
animate.min.css
495 ms
sppagebuilder.css
906 ms
sppagecontainer.css
686 ms
magnific-popup.css
687 ms
css
44 ms
css
51 ms
bootstrap.min.css
920 ms
font-awesome.min.css
704 ms
ha_greencare.css
730 ms
font-awesome.css
49 ms
custom_Default.css
914 ms
legacy.css
916 ms
template.css
1177 ms
preset1.css
965 ms
adjust_greencare.css
1133 ms
hikashop.css
1142 ms
hikashop_column.css
1144 ms
pagebuilder.css
1148 ms
hikashop.css
1202 ms
frontend_default.css
1360 ms
frontend-edit.css
1370 ms
style.css
1373 ms
css
49 ms
frontend.css
1378 ms
jquery.min.js
1649 ms
jquery-noconflict.js
1435 ms
core.js
1586 ms
jquery-migrate.min.js
1597 ms
parallax.min.js
1601 ms
sppagebuilder.js
1608 ms
jquery.magnific-popup.min.js
1671 ms
bootstrap.min.js
1814 ms
jquery.sticky.js
1825 ms
main.js
1830 ms
hikashop.js
1839 ms
frontend-edit.js
1890 ms
frontend.js
2277 ms
fontawesome.css
2047 ms
logo-green250.jpg
472 ms
greencare-hor.jpg
228 ms
customer-chat.png
501 ms
nexus-golf-001.jpg
1665 ms
bukit-beruntung-golf.jpg
1830 ms
angkatan-tentera.jpg
1610 ms
danau-img-002.jpg
1591 ms
clearwater.jpg
1889 ms
sld-18-003-min.jpg
1635 ms
sld-18-001-min.jpg
1821 ms
sld-18-002-min.jpg
1843 ms
sld-18-004-min.jpg
2090 ms
gcsaa2.jpg
1901 ms
gcsaa1.jpg
2047 ms
img001.jpg
2061 ms
img003.jpg
2079 ms
bg001.jpg
2127 ms
about-img2.jpg
2137 ms
img002.jpg
2275 ms
pest-control-0.jpg
2293 ms
facebook.png
2309 ms
mail.png
2318 ms
call.png
2362 ms
footer-bg.jpg
2372 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
31 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff
31 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff
32 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff
31 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff
32 ms
0QI6MX1D_JOuGQbT0gvTJPa787z5vBJFkqs.woff
178 ms
0QI6MX1D_JOuGQbT0gvTJPa787weuxJFkqs.woff
72 ms
fontawesome-webfont.woff
2639 ms
fontawesome-webfont.woff
22 ms
fontawesome-webfont.woff
2521 ms
fontawesome-webfont.woff
2539 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexg.woff
31 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexg.woff
32 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexg.woff
32 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexg.woff
33 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexg.woff
33 ms
KFOlCnqEu92Fr1MmWUlvAA.woff
55 ms
KFOmCnqEu92Fr1Me5g.woff
56 ms
KFOlCnqEu92Fr1MmSU5vAA.woff
55 ms
fontawesome-webfont.ttf
376 ms
greencare.com.my 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.
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
greencare.com.my 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
greencare.com.my 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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greencare.com.my can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Greencare.com.my 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.
greencare.com.my
Open Graph description is not detected on the main page of Greencare. 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: