3.2 sec in total
355 ms
2.8 sec
91 ms
Click here to check amazing Greenleaf content for United States. Otherwise, check out these important facts you probably never knew about greenleaf.technology
Visit greenleaf.technologyWe analyzed Greenleaf.technology page load time and found that the first response time was 355 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
greenleaf.technology performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value3.2 s
72/100
25%
Value3.0 s
94/100
10%
Value170 ms
92/100
30%
Value0.007
100/100
15%
Value3.8 s
89/100
10%
355 ms
293 ms
368 ms
551 ms
281 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Greenleaf.technology, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Hd.life.
Page size can be reduced by 657.6 kB (74%)
893.9 kB
236.3 kB
In fact, the total size of Greenleaf.technology main page is 893.9 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. 35% of websites need less resources to load. Javascripts take 887.5 kB which makes up the majority of the site volume.
Potential reduce by 5.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. This page needs HTML code to be minified as it can gain 880 B, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 5.1 kB or 79% of the original size.
Potential reduce by 652.5 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 652.5 kB or 74% of the original size.
Number of requests can be reduced by 49 (92%)
53
4
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greenleaf. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.hd.life
355 ms
jquery-ui.css
293 ms
jquery.mCustomScrollbar.min.css
368 ms
style.css
551 ms
responsive.css
281 ms
animate.css
376 ms
ngAnimate.css
287 ms
jquery.min.js
654 ms
jquery-ui.min.js
876 ms
jquery.ui.touch-punch.min.js
515 ms
validations.js
563 ms
helper.js
600 ms
wow.min.js
706 ms
angular.min.js
914 ms
angular-route.min.js
731 ms
angular-ui-router.min.js
785 ms
angular-animate.js
933 ms
angular-scroll.min.js
899 ms
jquery.mCustomScrollbar.concat.min.js
932 ms
scrollbars.min.js
1010 ms
angular-touch.min.js
1066 ms
angular-carousel.css
1085 ms
angular-carousel.js
1094 ms
slider.js
1096 ms
app.js
1154 ms
APIInterceptor.js
1230 ms
app-config.js
1260 ms
rootController.js
1275 ms
replace.js
1316 ms
accessibleForm.js
1316 ms
ngMin.js
1377 ms
ngMax.js
1453 ms
ngAlpha.js
1496 ms
ngAlphaSpace.js
1507 ms
ngValidEmail.js
1538 ms
emailAvailable.js
1497 ms
phoneAvailable.js
1483 ms
fieldMatch.js
1406 ms
backToTop.js
1455 ms
AuthFactory.js
1435 ms
UserFactory.js
1379 ms
ContactUsFactory.js
1390 ms
PlansFactory.js
1281 ms
contactUsCtrl.js
1314 ms
app.js
1384 ms
directive.js
1339 ms
landingCtrl.js
1269 ms
featuresCtrl.js
1288 ms
app.js
1292 ms
directive.js
1312 ms
controller.js
1229 ms
logo.gif
208 ms
analytics.js
47 ms
collect
26 ms
collect
63 ms
ga-audiences
37 ms
greenleaf.technology 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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
greenleaf.technology 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
greenleaf.technology SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greenleaf.technology can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Greenleaf.technology 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.
greenleaf.technology
Open Graph description is not detected on the main page of Greenleaf. 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: