8.6 sec in total
689 ms
7.7 sec
182 ms
Visit mortino.com now to see the best up-to-date Mortino content for Greece and also check out these interesting facts you probably never knew about mortino.com
Carnival Costumes Mortino Group Homepage
Visit mortino.comWe analyzed Mortino.com page load time and found that the first response time was 689 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
mortino.com performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value10.9 s
0/100
25%
Value10.3 s
8/100
10%
Value90 ms
98/100
30%
Value0.081
94/100
15%
Value7.8 s
45/100
10%
689 ms
1574 ms
25 ms
654 ms
274 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 89% of them (57 requests) were addressed to the original Mortino.com, 3% (2 requests) were made to Staticxx.facebook.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Mortino.com.
Page size can be reduced by 1.1 MB (57%)
1.9 MB
823.7 kB
In fact, the total size of Mortino.com main page is 1.9 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. 35% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 40.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. This page needs HTML code to be minified as it can gain 7.1 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 40.0 kB or 78% of the original size.
Potential reduce by 687.3 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. Obviously, Mortino needs image optimization as it can save up to 687.3 kB or 50% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 356.6 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 356.6 kB or 74% of the original size.
Potential reduce by 1.5 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. Mortino.com needs all CSS files to be minified and compressed as it can save up to 1.5 kB or 72% of the original size.
Number of requests can be reduced by 30 (49%)
61
31
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mortino. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
mortino.com
689 ms
1574 ms
css
25 ms
mootools-core.js
654 ms
core.js
274 ms
modal.js
282 ms
jquery.min.js
28 ms
k2.js
279 ms
bootstrap.js
546 ms
script.js
445 ms
menu.js
551 ms
responsive.js
546 ms
vmprices2.js
547 ms
vmsite.js
728 ms
facebox.js
816 ms
vmprices.js
824 ms
jquery.carouFredSel-6.1.0-packed.js
986 ms
1695 ms
jquery.themepunch.plugins.min.js
1062 ms
jquery.themepunch.revolution.min.js
1265 ms
iview.pack.js
1102 ms
jquery.mCustomScrollbar.js
1219 ms
linescript.js
1122 ms
en.jpg
364 ms
gr.jpg
511 ms
de.jpg
554 ms
fr.jpg
559 ms
it.jpg
648 ms
ru.jpg
653 ms
user.png
1100 ms
system.css
172 ms
main_boxed.jpg
283 ms
logo.png
421 ms
topbar-m.png
336 ms
new.png
284 ms
slide1.png
1415 ms
GreatNew.png
748 ms
slide2.png
1605 ms
image1.jpg
1112 ms
b49_280x280.jpg
612 ms
b729_280x280.jpg
717 ms
b871_280x280.jpg
901 ms
1_280x280.jpg
999 ms
b39_280x280.jpg
1024 ms
b452_280x280.jpg
1184 ms
iso_logo.jpg
1284 ms
ce_logo.jpg
1312 ms
new.png
1403 ms
list_arrows.png
1475 ms
up-arrow.png
1556 ms
footer_list_arrows.png
1623 ms
foot_marker.gif
1662 ms
fontawesome-webfont.woff
1930 ms
all.js
269 ms
analytics.js
29 ms
timer.png
1717 ms
loader.gif
1796 ms
ajax-loader.gif
1851 ms
fancybox_loading.gif
1835 ms
115 ms
xd_arbiter.php
210 ms
xd_arbiter.php
424 ms
coloredbg.png
337 ms
arrows.png
432 ms
mortino.com accessibility score
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
mortino.com 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
mortino.com 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mortino.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 Mortino.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.
mortino.com
Open Graph data is detected on the main page of Mortino. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: