7.4 sec in total
1.1 sec
6 sec
359 ms
Click here to check amazing George Lizos content. Otherwise, check out these important facts you probably never knew about georgelizos.com
I help lightworkers find their life purpose and overcome the fears and limiting beliefs that prevent them from following it, through intuitive guidance,
Visit georgelizos.comWe analyzed Georgelizos.com page load time and found that the first response time was 1.1 sec and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
georgelizos.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value66.1 s
0/100
25%
Value29.0 s
0/100
10%
Value25,520 ms
0/100
30%
Value0.128
82/100
15%
Value37.1 s
0/100
10%
1070 ms
329 ms
606 ms
417 ms
428 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 42% of them (47 requests) were addressed to the original Georgelizos.com, 18% (20 requests) were made to Fonts.gstatic.com and 16% (18 requests) were made to Static.mailerlite.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Georgelizos.com.
Page size can be reduced by 1.7 MB (17%)
9.8 MB
8.1 MB
In fact, the total size of Georgelizos.com main page is 9.8 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. 75% 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 9.3 MB which makes up the majority of the site volume.
Potential reduce by 211.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. 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 211.1 kB or 84% of the original size.
Potential reduce by 1.5 MB
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. Obviously, George Lizos needs image optimization as it can save up to 1.5 MB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 591 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 972 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. Georgelizos.com has all CSS files already compressed.
Number of requests can be reduced by 65 (78%)
83
18
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of George Lizos. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
georgelizos.com
1070 ms
wc-blocks-vendors-style.css
329 ms
wc-blocks-style.css
606 ms
light-box-styles.css
417 ms
swiper.min.css
428 ms
mailerlite_forms.css
420 ms
woocommerce-layout.css
602 ms
woocommerce.css
924 ms
swiper-bundle.min.css
802 ms
font-awesome.min.css
906 ms
wp-carousel-free-public.min.css
756 ms
style.css
1099 ms
css
29 ms
style.css
920 ms
style.min.css
1000 ms
style.css
954 ms
jquery.min.js
1349 ms
jquery-migrate.min.js
1087 ms
public.js
1140 ms
swiper.min.js
1624 ms
jquery.blockUI.min.js
1268 ms
add-to-cart.min.js
1041 ms
js.cookie.min.js
1457 ms
woocommerce.min.js
1444 ms
cart-fragments.min.js
1545 ms
swiper-bundle.min.js
1847 ms
wp-carousel-free-public.min.js
1701 ms
idle-timer.min.js
1544 ms
custom.js
1852 ms
scripts.min.js
2253 ms
smoothscroll.js
1861 ms
jquery.fitvids.js
2217 ms
frontend-bundle.min.js
2217 ms
jquery.validate.min.js
2254 ms
wc-gateway-ppec-order-review.js
2252 ms
common.js
2248 ms
smush-lazy-load.min.js
2531 ms
724e0541d3695d6e182ca12ca654d065ab3000c2.js
74 ms
v652eace1692a40cfa3763df669d7439c1639079717194
61 ms
init.js
179 ms
universal.js
142 ms
universal.js
177 ms
S6u9w4BMUTPHh6UVSwaPHw.woff
114 ms
S6u9w4BMUTPHh6UVSwaPHA.ttf
114 ms
S6u9w4BMUTPHh50XSwaPHw.woff
112 ms
S6u9w4BMUTPHh50XSwaPHA.ttf
121 ms
S6uyw4BMUTPHjxAwWA.woff
123 ms
S6uyw4BMUTPHjxAwWw.ttf
135 ms
S6u9w4BMUTPHh7USSwaPHw.woff
122 ms
S6u9w4BMUTPHh7USSwaPHA.ttf
135 ms
S6u8w4BMUTPHh30AUi-s.woff
121 ms
S6u8w4BMUTPHh30AUi-v.ttf
133 ms
S6u8w4BMUTPHjxsAUi-s.woff
174 ms
S6u8w4BMUTPHjxsAUi-v.ttf
178 ms
S6u_w4BMUTPHjxsI9w2_FQfr.woff
134 ms
S6u_w4BMUTPHjxsI9w2_FQfo.ttf
176 ms
S6u-w4BMUTPHjxsIPx-mPCQ.woff
177 ms
S6u-w4BMUTPHjxsIPx-mPCc.ttf
175 ms
S6u_w4BMUTPHjxsI5wq_FQfr.woff
175 ms
S6u_w4BMUTPHjxsI5wq_FQfo.ttf
181 ms
S6u_w4BMUTPHjxsI3wi_FQfr.woff
176 ms
S6u_w4BMUTPHjxsI3wi_FQfo.ttf
176 ms
modules.ttf
1321 ms
et-divi-dynamic-3905-late.css
1194 ms
universal.css
87 ms
u5p6s0a4g3_popups.js
224 ms
page.html
237 ms
page.html
211 ms
page.html
211 ms
page.html
198 ms
page.html
211 ms
VKAwbAL52
123 ms
style.css
60 ms
bootstrap-4.3.1.min.css
79 ms
jquery-3.3.1.slim.min.js
113 ms
popper.min.js
41 ms
bootstrap-4.3.1.min.js
133 ms
webforms.min.js
21 ms
bootstrap-4.3.1.min.css
90 ms
jquery-3.3.1.slim.min.js
153 ms
bootstrap-4.3.1.min.js
161 ms
webforms.min.js
40 ms
webforms.min.js
60 ms
jquery.min.js
69 ms
import.css
319 ms
import.css
39 ms
import.css
30 ms
import.css
34 ms
import.css
19 ms
css
74 ms
ml_jQuery.inputmask.bundle.min.js
239 ms
71982cf7cf68c40acdc821e921b12537352ee0f9.png
454 ms
6f0ccb7305b8b44d65e2f6974952f048d1d6c227.png
387 ms
692f2e2908db7ea81b2746a92892730181b647c0.png
378 ms
024786f894351ca9da1bff8de3f60dec0eefe229.png
384 ms
S6uyw4BMUTPHjxAwWA.woff
146 ms
S6u9w4BMUTPHh6UVSwaPHw.woff
164 ms
S6u_w4BMUTPHjxsI5wq_FQfr.woff
218 ms
S6u8w4BMUTPHjxsAUi-s.woff
217 ms
KFOmCnqEu92Fr1Mu7GxM.woff
217 ms
KFOlCnqEu92Fr1MmWUlfChc-.woff
215 ms
o-0NIpQlx3QUlC5A4PNjXhFVatyH.woff
215 ms
o-0IIpQlx3QUlC5A4PNr6zRG.woff
218 ms
george-lizos-logo-black-lato.png
603 ms
life-purposeproven-guide-lightworker.png
843 ms
2-copy-2.png
1191 ms
landscape-4.png
642 ms
modules.js
66 ms
georgelizos.com
521 ms
home-page-min-1.jpg
84 ms
woocommerce-smallscreen.css
321 ms
style.min.css
493 ms
style.min.css
49 ms
georgelizos.com 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
georgelizos.com 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
georgelizos.com 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
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 Georgelizos.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 Georgelizos.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.
georgelizos.com
Open Graph data is detected on the main page of George Lizos. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: