2.5 sec in total
59 ms
1.5 sec
956 ms
Click here to check amazing E Gree content. Otherwise, check out these important facts you probably never knew about e-gree.app
E-gree: convenient legal contracts for everyday needs. In the palm of your hand. We have over 20 forms for quick, simple, and legal contracts for everyday needs
Visit e-gree.appWe analyzed E-gree.app page load time and found that the first response time was 59 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
e-gree.app performance score
name
value
score
weighting
Value1.8 s
89/100
10%
Value4.4 s
39/100
25%
Value2.5 s
98/100
10%
Value710 ms
42/100
30%
Value0.031
100/100
15%
Value7.5 s
47/100
10%
59 ms
428 ms
14 ms
27 ms
39 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 96% of them (98 requests) were addressed to the original E-gree.app, 2% (2 requests) were made to Googletagmanager.com and 1% (1 request) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (888 ms) relates to the external source Mc.yandex.ru.
Page size can be reduced by 274.3 kB (4%)
7.7 MB
7.4 MB
In fact, the total size of E-gree.app main page is 7.7 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. Only a small number of websites need less resources to load. Images take 7.4 MB which makes up the majority of the site volume.
Potential reduce by 49.0 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 49.0 kB or 83% of the original size.
Potential reduce by 224.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. E Gree images are well optimized though.
Potential reduce by 594 B
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 102 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. E-gree.app has all CSS files already compressed.
Number of requests can be reduced by 21 (23%)
91
70
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Gree. 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 as a result speed up the page load time.
e-gree.app
59 ms
e-gree.app
428 ms
autoptimize_2115dcd299cbd06b21c3f2318e986856.css
14 ms
jquery.min.js
27 ms
jquery-migrate.min.js
39 ms
slick.min.js
39 ms
scripts.min.js
27 ms
autoptimize_single_17a7808bcfe344e402414fbea7ec1161.js
42 ms
regenerator-runtime.min.js
76 ms
wp-polyfill.min.js
77 ms
autoptimize_single_6ad9165b167d54947b37f4b9de75ab39.js
81 ms
wp-ulike.min.js
86 ms
wp-embed.min.js
87 ms
mobile-detect.min.js
69 ms
gtm.js
174 ms
gtm.js
197 ms
tag.js
888 ms
icon-logo.svg
25 ms
main-bottom-bg.svg
159 ms
app-store-image.svg
19 ms
google-play-image.svg
17 ms
phones-image.png
161 ms
legal-image.svg
165 ms
Handyman_700%D1%85320-700x320.png
164 ms
Handyman_460%D1%85280-460x280.png
188 ms
contracts-item-bg.svg
160 ms
Handyman-150x150.png
188 ms
Venue-700x320-1.png
190 ms
Venue-460x280-1.png
193 ms
icon-venue.svg
188 ms
Freelance-700x320-1.png
191 ms
Freelance-460x280-1.png
221 ms
icon-freelance.svg
192 ms
700-%D1%85-320-4-700x320.png
230 ms
460%D1%85280-460x280.png
224 ms
Icon_Promise.svg
219 ms
Rental-700x320-1.png
222 ms
Rental-460x280-1.png
223 ms
icon-rental.svg
225 ms
Purchase-and-Sale-700x320-1.png
271 ms
Purchase-and-Sale-460x280-1.png
230 ms
icon-purchase_and_sale.svg
228 ms
Date-700x320-1.png
309 ms
Date-460x280-1.png
314 ms
icon-date.svg
276 ms
Uncouple-700x320-1.png
335 ms
Uncouple-460x280-1.png
273 ms
icon-uncouple.svg
318 ms
Prenup-700x320-1.png
358 ms
Prenup-460x280-1.png
352 ms
icon-prenup.svg
336 ms
Couple-700x320-1.png
388 ms
Couple-460x280-1.png
351 ms
icon-couple.svg
358 ms
icon-allowance.svg
394 ms
icon-consent.svg
384 ms
icon-event.svg
255 ms
icon-idea.svg
252 ms
icon-refer.svg
268 ms
icon-secret.svg
261 ms
icon-sexting.svg
282 ms
protect-image.svg
272 ms
sign-top-bg.svg
266 ms
sign-bottom-bg.svg
272 ms
moon-image.svg
279 ms
earth-image.svg
294 ms
1086%D1%85496-5-1080x494.png
313 ms
Recoleta-Regular.woff
326 ms
Recoleta-Medium.woff
317 ms
Recoleta-Light.woff
333 ms
Recoleta-Thin.woff
315 ms
Recoleta-SemiBold.woff
338 ms
Recoleta-Bold.woff
357 ms
Recoleta-Black.woff
376 ms
icomoon.ttf
352 ms
%D0%9E%D0%B1%D0%BB%D0%BE%D0%B6%D0%BA%D0%B0-1920%D1%85420-2-700x320.png
432 ms
%D0%9E%D0%B1%D0%BB%D0%BE%D0%B6%D0%BA%D0%B0-340%D1%85260-2-340x260.png
402 ms
%D0%9E%D0%B1%D0%BB%D0%BE%D0%B6%D0%BA%D0%B0-1920%D1%85420-1-700x320.png
329 ms
%D0%9E%D0%B1%D0%BB%D0%BE%D0%B6%D0%BA%D0%B0-340%D1%85260-1-340x260.png
334 ms
Promise_1920%D1%85420-700x320.png
353 ms
Promise_340%D1%85260-340x260.png
351 ms
1920%D1%85420-3-700x320.png
323 ms
700-%D1%85-320-3-340x260.png
347 ms
logo-forbes@2x.png
337 ms
logo-cheddar@2x.png
328 ms
Metro-Logo.png
312 ms
MacTech_Logo-ForAllAppleTechs-240x75-1.png
330 ms
Huck-Logo.png
315 ms
1200px-The_Sun.svg_.png
337 ms
law.com-logo.png
325 ms
Vodianova-150x150.png
326 ms
Kahawaty%E2%80%8B-150x150.png
310 ms
Frame-1606-150x150.png
330 ms
phones-image-small.png
325 ms
agree-bg-top.svg
331 ms
agree-bg-bottom.svg
311 ms
icon-fb.svg
333 ms
icon-instagram.svg
337 ms
icon-tiktok.svg
325 ms
icon-twitter.svg
317 ms
icon-linkedin.svg
325 ms
footer-image.svg
324 ms
e-gree.app accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
e-gree.app 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
Browser errors were logged to the console
e-gree.app SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-gree.app 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 E-gree.app 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.
e-gree.app
Open Graph data is detected on the main page of E Gree. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: