1.7 sec in total
32 ms
1.3 sec
349 ms
Click here to check amazing Alwaysgreen content. Otherwise, check out these important facts you probably never knew about alwaysgreen.com
Visit alwaysgreen.comWe analyzed Alwaysgreen.com page load time and found that the first response time was 32 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
alwaysgreen.com performance score
32 ms
226 ms
85 ms
181 ms
63 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Alwaysgreen.com, 35% (25 requests) were made to Tg-cdn.azureedge.net and 13% (9 requests) were made to Trugreen.com. The less responsive or slowest element that took the longest time to load (522 ms) relates to the external source Trugreen.com.
Page size can be reduced by 115.9 kB (17%)
696.9 kB
581.0 kB
In fact, the total size of Alwaysgreen.com main page is 696.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. 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 350.5 kB which makes up the majority of the site volume.
Potential reduce by 88.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 88.3 kB or 77% of the original size.
Potential reduce by 24.7 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. Alwaysgreen images are well optimized though.
Potential reduce by 2.7 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 203 B
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. Alwaysgreen.com has all CSS files already compressed.
Number of requests can be reduced by 51 (76%)
67
16
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Alwaysgreen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
alwaysgreen.com
32 ms
always-green-trugreen
226 ms
optimize.js
85 ms
gtm.js
181 ms
cookieconsent.min.css
63 ms
css_v52pnKvzGMwJsCsbQob1gLXKl-3n3S7iFQHISwvruAA.css
62 ms
css_grUTbJNkSaNaXFdFR_vqfzlFDFp-pdQ5QYmFyi2RRpo.css
73 ms
css_ggsBoX3hTJpA7efAX2wH7CnKof3nO7BDUMXEpUkB9uQ.css
103 ms
css_nNQ8Vl1HS0B9SuwTWsdzBJH4cKRWsLWEoeIjgH0wn-U.css
115 ms
fullcalendar.min.css
62 ms
css_gicmJGx2bQmuMv8JsOAcp0kDu22AonqZyF-3mM8U1VU.css
112 ms
css
75 ms
js_v2hQKSQ0jfTHuJj02e3aWvpF6ljiyDCxjxCbISFKEy4.js
119 ms
js_TF648nQzyfCG-kneL1ucHOmjRbs0tGd_QcAdu3x_R9g.js
110 ms
js_AipHM08eF05kKI3B6CYUr9cy1AR-F-7M7M31wLcVkyI.js
134 ms
js_8DcejqiC9MQqBCGdHDQzXcCfLpxaSgqqh4M0mRvGaa0.js
136 ms
search-script.min.js
78 ms
js_luRTp0sUecP1wshg11FnDC0wlz43L9NyAhhEAhjNqwA.js
158 ms
cookieconsent.min.js
69 ms
js_rJxNjixoRXXEvqg7rMbO45SNLZILxp--pZXrV5sJEQU.js
174 ms
vendors.bundle.js
175 ms
commons.bundle.js
216 ms
loyality.bundle.js
174 ms
js_Ui7KMSgq7Ve5D9xF1O9d9-4DV5teAnq4S6DKefIgI5A.js
174 ms
header.bundle.js
176 ms
js_XgE4pDlYxFFJq0raeNRQVnf4U4F6nkP6eq7DZYj1lnA.js
213 ms
weather-icons.min.css
71 ms
all.css
427 ms
cludo-search.min.css
211 ms
plus.svg
271 ms
trugreen-1000545.js
492 ms
logo.svg
228 ms
tg-mobile-logo.svg
224 ms
acq%20tile_15_3.jpg
231 ms
Always%20Green%20and%20Trugreen%20Logo.png
229 ms
logo-NALP-Primary-REVERSE_0.png
228 ms
tg-pga-18.png
228 ms
loading-animation.gif
230 ms
appstore.png
419 ms
googleplay.png
420 ms
facebook.svg
522 ms
twitter.svg
517 ms
pinterest.svg
518 ms
null
521 ms
trugreen-close.svg
515 ms
conversion_async.js
250 ms
analytics.js
358 ms
bat.js
354 ms
core.js
348 ms
fbevents.js
316 ms
nas.v1.min.js
411 ms
ytag.min.js
338 ms
web-vitals.es5.umd.min.js
313 ms
js
199 ms
acq%20hero_15_3.jpg
266 ms
activityi;src=8299733;type=retarget;cat=trugr0;ord=6438018302806;gtm=2wga30;auiddc=329329855.1665008646;u2=https%3A%2F%2Fwww.trugreen.com%2Flawn-care-101%2Fblog%2Falways-green-trugreen%3FVar201%3D3;~oref=https%3A%2F%2Fwww.trugreen.com%2Flawn-care-101%2Fblog%2Falways-green-trugreen%3FVar201%3D3
387 ms
28507d59-1ca4-47c6-87a6-e702096e2271.js
340 ms
302 ms
309 ms
1480934288894003
87 ms
main.3a217bc7.js
80 ms
collect
60 ms
5268676.js
108 ms
collect
90 ms
166329607067898
15 ms
55 ms
5268676
174 ms
56 ms
ga-audiences
24 ms
src=8299733;type=retarget;cat=trugr0;ord=6438018302806;gtm=2wga30;auiddc=329329855.1665008646;u2=https%3A%2F%2Fwww.trugreen.com%2Flawn-care-101%2Fblog%2Falways-green-trugreen%3FVar201%3D3;~oref=https%3A%2F%2Fwww.trugreen.com%2Flawn-care-101%2Fblog%2Falways-green-trugreen%3FVar201%3D3
29 ms
iui3
28 ms
alwaysgreen.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Alwaysgreen.com 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 Alwaysgreen.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.
alwaysgreen.com
Open Graph description is not detected on the main page of Alwaysgreen. 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: