4.4 sec in total
319 ms
3.4 sec
720 ms
Click here to check amazing Discovery Safari content. Otherwise, check out these important facts you probably never knew about discovery-safari.gr
Explore the real Crete! Join us in one of our exciting and memorable quad - buggy or Jeep tours. All our activities are under the direct supervision of qualified guides.
Visit discovery-safari.grWe analyzed Discovery-safari.gr page load time and found that the first response time was 319 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
discovery-safari.gr performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value9.6 s
0/100
25%
Value11.1 s
6/100
10%
Value2,630 ms
4/100
30%
Value0.488
17/100
15%
Value23.5 s
1/100
10%
319 ms
1104 ms
189 ms
285 ms
292 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 72% of them (71 requests) were addressed to the original Discovery-safari.gr, 8% (8 requests) were made to Embed.tawk.to and 5% (5 requests) were made to Static.tacdn.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Discovery-safari.gr.
Page size can be reduced by 271.6 kB (13%)
2.1 MB
1.8 MB
In fact, the total size of Discovery-safari.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. 60% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 37.9 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 37.9 kB or 74% of the original size.
Potential reduce by 38.2 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 Safari images are well optimized though.
Potential reduce by 56.8 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. This website has mostly compressed JavaScripts.
Potential reduce by 138.7 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. Discovery-safari.gr needs all CSS files to be minified and compressed as it can save up to 138.7 kB or 59% of the original size.
Number of requests can be reduced by 61 (67%)
91
30
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Discovery Safari. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
discovery-safari.gr
319 ms
discovery-safari.gr
1104 ms
style.min.css
189 ms
theme.min.css
285 ms
styles.css
292 ms
settings.css
295 ms
fontello.css
296 ms
wpcloudy.min.css
292 ms
css
40 ms
reset.css
293 ms
960.css
380 ms
superfish.css
388 ms
font-awesome.min.css
389 ms
style.css
485 ms
custom_style.css
391 ms
responsive.css
392 ms
fluid.css
474 ms
front.min.css
482 ms
tmy-styles.css
488 ms
jquery.min.js
580 ms
jquery-migrate.min.js
493 ms
css
31 ms
wpcloudy-anim.min.css
482 ms
rs6.css
591 ms
wp-polyfill.min.js
604 ms
hooks.min.js
530 ms
i18n.min.js
531 ms
lodash.min.js
600 ms
url.min.js
603 ms
api-fetch.min.js
602 ms
index.js
601 ms
rbtools.min.js
700 ms
rs6.min.js
896 ms
wp-cloudy-ajax.js
702 ms
superfish.combined.js
700 ms
script.js
701 ms
jquery.meanmenu.min.js
701 ms
jquery.meanmenu.options.js
803 ms
front.min.js
804 ms
tmy-scripts.js
805 ms
wejs
450 ms
wp-embed.min.js
709 ms
analytics.js
95 ms
design_image_kayak_travel-guides_circle_orange_find-us-on-tg_150x150_20022x.png
144 ms
medium-logo-12097-2.png
159 ms
logo_234x90.png
297 ms
dummy.png
394 ms
favicon-300x300.png
588 ms
IMG_5075.jpg
587 ms
quadsitefinal.jpg
681 ms
luxsite-2.jpeg
493 ms
viator-300x300.png
475 ms
adrenaline_hunter-300x300.png
491 ms
gyg_logo-300x300.png
571 ms
bookmundi-300x300.png
588 ms
R0eland.jpg
589 ms
lpope615.jpg
667 ms
JCH400.jpg
683 ms
dimitravilla.jpg
686 ms
tui_200_bg.png
684 ms
lookea_200.png
685 ms
tripadvisor_200.png
762 ms
Horizontal_Banner_trans_all.png
757 ms
tmy-styles.css
757 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
127 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
135 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf
142 ms
intro_bg_down.png
758 ms
WidgetEmbed-cdswritereviewlg
184 ms
default
324 ms
fontawesome-webfont.woff
787 ms
white_bg.png
691 ms
bacroundpol.jpg
1052 ms
repeat-x-sprite-sheet.png
780 ms
wp-polyfill-fetch.min.js
751 ms
collect
38 ms
wp-polyfill-dom-rect.min.js
736 ms
tg005.png
4 ms
js
130 ms
wp-polyfill-url.min.js
690 ms
wp-polyfill-formdata.min.js
777 ms
wp-polyfill-element-closest.min.js
779 ms
wp-polyfill-object-fit.min.js
781 ms
misc-sprite-sheet.png
898 ms
t4b_widget_war_large-v2360815526a.css
21 ms
cdswidgets_m-c-v22480917520a.js
30 ms
footer_bg.jpg
804 ms
iframe_api
60 ms
www-widgetapi.js
7 ms
Tripadvisor_lockup_horizontal_secondary_registered.svg
8 ms
styleguide-v22291400912a.css
9 ms
twk-event-polyfill.js
52 ms
twk-main.js
65 ms
twk-vendor.js
162 ms
twk-chunk-vendors.js
181 ms
twk-chunk-common.js
188 ms
twk-runtime.js
97 ms
twk-app.js
99 ms
TripAdvisor_Regular.woff
5 ms
discovery-safari.gr accessibility score
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
Form elements do not have associated labels
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.
discovery-safari.gr 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
discovery-safari.gr 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
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 Discovery-safari.gr 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 Discovery-safari.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.
discovery-safari.gr
Open Graph data is detected on the main page of Discovery Safari. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: