4.9 sec in total
1.2 sec
3.1 sec
629 ms
Click here to check amazing Greenolivedigital content. Otherwise, check out these important facts you probably never knew about greenolivedigital.com
Visit greenolivedigital.comWe analyzed Greenolivedigital.com page load time and found that the first response time was 1.2 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
greenolivedigital.com performance score
1169 ms
219 ms
28 ms
250 ms
35 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Greenolivedigital.com, 13% (9 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Cloud.webtype.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Greenoliveme.com.
Page size can be reduced by 2.2 MB (49%)
4.4 MB
2.3 MB
In fact, the total size of Greenolivedigital.com main page is 4.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 1.8 MB which makes up the majority of the site volume.
Potential reduce by 33.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 33.0 kB or 81% of the original size.
Potential reduce by 18.5 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. Greenolivedigital images are well optimized though.
Potential reduce by 841.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 841.7 kB or 72% of the original size.
Potential reduce by 1.3 MB
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. Greenolivedigital.com needs all CSS files to be minified and compressed as it can save up to 1.3 MB or 90% of the original size.
Number of requests can be reduced by 35 (61%)
57
22
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greenolivedigital. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
greenoliveme.com
1169 ms
490efe92-1262-4fde-bdad-3b35048a11cc.css
219 ms
css
28 ms
layerslider.css
250 ms
css
35 ms
styles.css
168 ms
style.css
168 ms
font-awesome.min.css
273 ms
style.min.css
251 ms
stylesheet.min.css
730 ms
style_dynamic.css
332 ms
responsive.min.css
417 ms
style_dynamic_responsive.css
332 ms
js_composer.css
1092 ms
custom_css.css
358 ms
greensock.js
568 ms
jquery.js
593 ms
jquery-migrate.min.js
445 ms
layerslider.kreaturamedia.jquery.js
570 ms
layerslider.transitions.js
529 ms
layerslider.custom.transitions.js
613 ms
jquery.form.min.js
570 ms
scripts.js
573 ms
qode-like.min.js
596 ms
plugins.js
1278 ms
jquery.carouFredSel-6.2.1.min.js
738 ms
lemmon-slider.min.js
661 ms
jquery.fullPage.min.js
690 ms
jquery.mousewheel.min.js
715 ms
jquery.touchSwipe.min.js
741 ms
isotope.pkgd.min.js
763 ms
default_dynamic.js
799 ms
default.min.js
989 ms
custom_js.js
825 ms
comment-reply.min.js
847 ms
js_composer_front.js
886 ms
wp-embed.min.js
909 ms
wp-emoji-release.min.js
854 ms
v.gif
81 ms
GreenOlive_Logo_Black.png
98 ms
GreenOlive_Logo_White.png
98 ms
slide1.jpg
350 ms
Slide2.jpg
539 ms
Slide3.jpg
346 ms
Slide4.jpg
537 ms
Audi_01-500x380.jpg
347 ms
Dubai_International_Airport_cover-500x380.jpg
344 ms
brochure_mockup-500x380.jpg
348 ms
thePad-500x380.jpg
349 ms
GreenOliveDigital_02-500x380.jpg
349 ms
ICON11.png
350 ms
ICON21.png
356 ms
ICON6.png
534 ms
ICON31.png
535 ms
ICON41.png
536 ms
ICON51.png
537 ms
Contact-Green-Olive.jpg
539 ms
a028c49a-f898-4426-b783-46f4b2fc43ff
293 ms
STBOO2waD2LpX45SXYjQBS3USBnSvpkopQaUR-2r7iU.ttf
17 ms
WmVKXVcOuffP_qmCpFuyzS3USBnSvpkopQaUR-2r7iU.ttf
72 ms
QoPu455RxV2raYSIFXAMBS3USBnSvpkopQaUR-2r7iU.ttf
19 ms
Ji5epXNcpHu3r63lhS0cTi3USBnSvpkopQaUR-2r7iU.ttf
71 ms
Li18TEFObx_yGdzKDoI_ci3USBnSvpkopQaUR-2r7iU.ttf
18 ms
do7-0avPC2vxor6SN2THGA.ttf
19 ms
ZKwULyCG95tk6mOqHQfRBC3USBnSvpkopQaUR-2r7iU.ttf
19 ms
cbAbzEjxTdN5KKmS-gA0tS3USBnSvpkopQaUR-2r7iU.ttf
71 ms
rr0ijB5_2nAJsAoZ6vECXaCWcynf_cDxXwCLxiixG1c.ttf
70 ms
fontawesome-webfont.woff
485 ms
23d30944-ffd3-482f-b094-eccc5c22c7f4
290 ms
ajax-loader.gif
86 ms
greenolivedigital.com SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greenolivedigital.com 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), while the claimed language is English. Our system also found out that Greenolivedigital.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.
greenolivedigital.com
Open Graph description is not detected on the main page of Greenolivedigital. 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: