11 sec in total
450 ms
10.1 sec
507 ms
Visit discoveryyachting.com now to see the best up-to-date Discovery Yacht Ing content and also check out these interesting facts you probably never knew about discoveryyachting.com
Corfu yacht charter,Sailing yacht charter Greece, Motor yacht charter segelyacht Corfu and Ionian islands, Marina Gouvia, Greek islands, Bareboat charter, Yachtcharter Korfu, location bateau voilier v...
Visit discoveryyachting.comWe analyzed Discoveryyachting.com page load time and found that the first response time was 450 ms and then it took 10.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
discoveryyachting.com performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value9.4 s
0/100
25%
Value8.4 s
19/100
10%
Value1,780 ms
10/100
30%
Value0.025
100/100
15%
Value13.1 s
12/100
10%
450 ms
437 ms
340 ms
992 ms
110 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 76% of them (87 requests) were addressed to the original Discoveryyachting.com, 17% (19 requests) were made to Booking-manager.com and 3% (3 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (6.1 sec) relates to the external source Booking-manager.com.
Page size can be reduced by 153.5 kB (6%)
2.4 MB
2.3 MB
In fact, the total size of Discoveryyachting.com main page is 2.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. 55% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 49.3 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.3 kB or 79% of the original size.
Potential reduce by 49.4 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. Discovery Yacht Ing images are well optimized though.
Potential reduce by 39.5 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 39.5 kB or 12% of the original size.
Potential reduce by 15.3 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. Discoveryyachting.com needs all CSS files to be minified and compressed as it can save up to 15.3 kB or 33% of the original size.
Number of requests can be reduced by 48 (44%)
108
60
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Discovery Yacht Ing. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
discoveryyachting.com
450 ms
discoveryyachting.com
437 ms
www.discoveryyachting.com
340 ms
www.discoveryyachting.com
992 ms
jscss.php
110 ms
attachments1.css
217 ms
attachments.css
307 ms
default.css
306 ms
mootools-core.js
410 ms
core.js
309 ms
caption.js
316 ms
mootools-more.js
432 ms
en_slimbox.js
410 ms
attachments_refresh.js
408 ms
modal.js
412 ms
menu.js
420 ms
equalheight.js
509 ms
totop.js
510 ms
autocompleter.js
512 ms
script.js
514 ms
wbm-alter.js
522 ms
system.css
431 ms
stylesheet.css
504 ms
ga.js
59 ms
gtm.js
101 ms
logo.jpg
125 ms
big_daddy.png
122 ms
ionian.jpg
123 ms
sporades.jpg
126 ms
cyclades.jpg
124 ms
3e6c33ebde272ecf9850bfa95a666961.jpg
125 ms
600x100_Banner_Charter_EN.png
263 ms
3208f108d042ad395500dbcefc87c559.png
349 ms
69299ab6b0599132a94a354f5f12360a.png
262 ms
0555ecf86369cf545ba0b2268b19105a.PNG
420 ms
2cb3e6a32caf9b934e20e301bd87ccbe.jpg
263 ms
fd6a8d8f27224d5032a58e1ab8c6f77d.JPG
261 ms
2871d5968ebcb831ca3447e13267cdbb.jpg
366 ms
0af200ead136aa26215dd20097e9c38e.JPG
363 ms
c37c1eda656989d0322ab36716b83d87.jpeg
363 ms
a50ff9ed4b61d49445f6ed704a3b91c8.jpg
465 ms
6a09cc1eb4a64f2a69068dfca845083a.jpeg
450 ms
38defe11a2159f7cca1ea72a13ea92d5.jpeg
463 ms
624c1af40840bbcf2813aa705e4e8fe6.jpeg
464 ms
afd59b9dbbe721089ee402c484ca72a4.jpeg
472 ms
1ea6c8055ac83fb17d12f4226363e1d7.jpeg
521 ms
de040cc853016994a5d127c0595294c0.jpg
552 ms
50ddc8d70ca8239bdb9211b7b511d671.jpg
565 ms
1d5a21c936b260183d3e2a57ea18ce5f.JPG
567 ms
7e58455c072f6421d5f7e78e27eeada4.jpg
566 ms
f114fa6d74f333ab982a7e12a1d779af.png
578 ms
2ee6470b1c0a84dd3210ccc724c105a8.jpg
622 ms
google_plus.png
653 ms
13ef566ae2570ad62a93e88816992130.JPG
668 ms
68d75ee465b471039695685397461c6f.png
668 ms
95fede9e54716626a3b14482b125498f.png
668 ms
4e5e87fa771e8a2b55b49765fcaa6f37.png
683 ms
30a994acb489c9b39228d5c02b619549.png
726 ms
4b6c68369dee31db1b5c8dbe124247af.png
754 ms
b5ed0323e53a75b8c42a99f47f201683.png
769 ms
0f74357dd8b37d4bc9c8bc40dfc9ccc0.jpg
759 ms
page.html
6128 ms
loader.js
208 ms
__utm.gif
28 ms
bebasneue-webfont.woff
660 ms
97a6709d98566f2cdf9dc254ca58ee0b.png
674 ms
754ce312da09361c79afff91f94c88d7.JPG
710 ms
b35a9a8830ca2ea19866008c872e98be.JPG
739 ms
853646b0fb305be4cc575466d3c80a7d.JPG
751 ms
js
47 ms
4df358eb4384b42e8e9be4c7816c4692.jpg
729 ms
4803d38ce4d724fb4a830052de1a8a11.jpg
630 ms
9059a098ab31458f650927aeecc33284.jpg
640 ms
8aac688c4099484f9721882a1d40515b.JPG
674 ms
b64a1876c36316b6f07357b7948a21c6.JPG
702 ms
7b8459c664680bff6a725bb593d0822b.JPG
631 ms
a6911fa108a5e68f4fea3ac7db804df5.png
616 ms
b0a5a8235977074040a30dca24400d98.JPG
633 ms
83632db94f510639c8c4e9360cd02583.png
644 ms
loading.gif
620 ms
btn_prev.png
616 ms
btn_next.png
617 ms
userpos-bg.png
615 ms
userpos-sep.gif
632 ms
border.gif
645 ms
icon_tweet.png
621 ms
icon_facebook.png
615 ms
breadcrumbs.png
621 ms
2.jpg
1138 ms
3.jpg
1046 ms
slide4.jpg
858 ms
1.jpg
927 ms
slide5.jpg
932 ms
fonts.css
308 ms
magnific-popup.css
308 ms
font-awesome.min.css
410 ms
jquery-ui.css
19 ms
jquery.min.js
23 ms
jquery-ui.min.js
26 ms
jquery.magnific-popup.js
511 ms
bootstrap.min.js
509 ms
slick.min.js
518 ms
wNumb.js
438 ms
userincr.js
517 ms
custom.js
521 ms
moment.min.js
550 ms
daterangepicker.js
612 ms
chosen.jquery.js
613 ms
jquery.ui.touch-punch.min.js
30 ms
tools.js
613 ms
accounting.min.js
612 ms
iframeResizer.contentWindow.min.js
615 ms
responsive_wbm.css
664 ms
fontawesome-webfont.woff
136 ms
chosen-sprite.png
520 ms
discoveryyachting.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
Form elements do not have associated labels
Links do not have a discernible name
discoveryyachting.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Browser errors were logged to the console
Page has valid source maps
discoveryyachting.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Discoveryyachting.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 Discoveryyachting.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.
discoveryyachting.com
Open Graph description is not detected on the main page of Discovery Yacht Ing. 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: