3.8 sec in total
300 ms
3.1 sec
392 ms
Welcome to liolios.gr homepage info - get ready to check Liolios best content for Greece right away, or after learning these important things about liolios.gr
Καλώς ήρθατε στο κατάστημα μας Λιόλιος Μουσικά Όργανα
Visit liolios.grWe analyzed Liolios.gr page load time and found that the first response time was 300 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
liolios.gr performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value9.7 s
0/100
25%
Value8.1 s
21/100
10%
Value2,630 ms
4/100
30%
Value0.45
20/100
15%
Value13.7 s
10/100
10%
300 ms
746 ms
49 ms
380 ms
670 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 72% of them (58 requests) were addressed to the original Liolios.gr, 10% (8 requests) were made to Fonts.gstatic.com and 6% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Liolios.gr.
Page size can be reduced by 842.6 kB (41%)
2.1 MB
1.2 MB
In fact, the total size of Liolios.gr main page is 2.1 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. Javascripts take 878.8 kB which makes up the majority of the site volume.
Potential reduce by 56.2 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 56.2 kB or 80% of the original size.
Potential reduce by 50.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. Liolios images are well optimized though.
Potential reduce by 498.1 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 498.1 kB or 57% of the original size.
Potential reduce by 237.8 kB
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. Liolios.gr needs all CSS files to be minified and compressed as it can save up to 237.8 kB or 76% of the original size.
Number of requests can be reduced by 22 (32%)
69
47
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Liolios. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
liolios.gr
300 ms
liolios.gr
746 ms
css
49 ms
all.min.css
380 ms
bootstrap.min.css
670 ms
aqua.min.css
384 ms
styles.css
487 ms
custom.css
394 ms
jquery.min.js
35 ms
aos.css
47 ms
style.css
393 ms
js
86 ms
api.js
54 ms
WebResource.axd
474 ms
ScriptResource.axd
574 ms
ScriptResource.axd
489 ms
bootstrap.min.js
496 ms
jquery.common.js
483 ms
platform.js
29 ms
aos.js
14 ms
recaptcha__en.js
60 ms
4918-mh-401frqmstblk-esp-ltd-guitar-38366-s.jpg
701 ms
logo-small.png
133 ms
callcenter.png
133 ms
supported-cards.png
134 ms
4912-ec-200-blks-esp-ltd-guitar-38364-s.jpg
734 ms
4909-b-10-kit-blk-esp-ltd-bass-38363-s.jpg
722 ms
4903-sn-200frrblk-esp-ltd-guitar-38357-s.jpg
733 ms
4897-mh-350fr-qm-dbsb-esp-ltd-guitar-38353-s.jpg
721 ms
4703-arc-6-blk-esp-guitar-s.jpg
733 ms
249-ec-1000-fm-asb-esp-ltd-guitar-amber-sunburst-s.jpg
793 ms
1979-ec-1000qm-esp-ltd-guitar-see-thru-black-cherry-s.jpg
824 ms
1978-ec-1000fm-fr-esp-ltd-guitar-see-thru-black-s.jpg
822 ms
2719-metallofwno-angel-ax-25n3-s.jpg
823 ms
2549-mg-50dfx-e-marshall-ki8aras-park-17427-s.jpg
824 ms
973-cs02719-sandp-cedar-s.jpg
824 ms
mf-01495-L7FI-s.jpg
886 ms
mf-01414-E07A-s.png
919 ms
mf-01360-RELO-s.jpg
918 ms
mf-01548-PBJM-s.jpg
916 ms
mf-01292-VHOR-s.jpg
917 ms
mf-01289-WJQT-s.png
918 ms
mf-01422-SEMP-s.png
980 ms
mf-01537-J5DF-s.png
1014 ms
mf-01487-SEMP-s.png
1013 ms
mf-01325-I4CF-s.jpg
1012 ms
mf-01503-N9HK-s.png
1013 ms
mf-01596-UGOR-s.jpg
1013 ms
mf-01331-G2AD-s.png
1075 ms
mf-01435-WIQT-s.jpg
1107 ms
mf-01550-VHPS-s.png
1107 ms
mf-01433-9U35-s.jpg
1107 ms
mf-01544-BX58-s.jpg
1108 ms
mf-01264-UGOR-s.jpg
1108 ms
mf-01570-G29C-s.gif
1169 ms
mf-01498-TFNQ-s.png
1201 ms
mf-01419-WIQT-s.png
1202 ms
mf-01405-N9HK-s.jpg
1202 ms
mf-01259-DY69-s.png
1202 ms
mf-01253-XKRU-s.jpg
1203 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
146 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
147 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
214 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
214 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
214 ms
fa-solid-900.woff
214 ms
fa-regular-400.woff
213 ms
anchor
152 ms
top.png
191 ms
styles__ltr.css
47 ms
recaptcha__en.js
49 ms
8NY0ran000JGuwjjrnGZuyoBb1n1tpfvDqq-fwWafx0.js
53 ms
webworker.js
212 ms
logo_48.png
202 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
126 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
125 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
124 ms
recaptcha__en.js
21 ms
b1b-slide1.jpg
749 ms
slide3.jpg
672 ms
slide4.jpg
756 ms
liolios.gr 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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
liolios.gr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
liolios.gr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EL
EL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Liolios.gr can be misinterpreted by Google and other search engines. Our service has detected that Greek is used on the page, and it matches the claimed language. Our system also found out that Liolios.gr 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.
liolios.gr
Open Graph description is not detected on the main page of Liolios. 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: