5.3 sec in total
1.3 sec
3.7 sec
224 ms
Visit yway.ch now to see the best up-to-date Yway content and also check out these interesting facts you probably never knew about yway.ch
Répertoire des indicateurs de randonnée pédestres suisses.
Visit yway.chWe analyzed Yway.ch page load time and found that the first response time was 1.3 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
yway.ch performance score
name
value
score
weighting
Value1.7 s
93/100
10%
Value1.7 s
99/100
25%
Value1.8 s
100/100
10%
Value0 ms
100/100
30%
Value0.032
100/100
15%
Value1.7 s
100/100
10%
1302 ms
203 ms
309 ms
215 ms
210 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 27% of them (29 requests) were addressed to the original Yway.ch, 37% (40 requests) were made to Maps.googleapis.com and 8% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Yway.ch.
Page size can be reduced by 696.4 kB (30%)
2.3 MB
1.6 MB
In fact, the total size of Yway.ch main page is 2.3 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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 47.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 47.2 kB or 84% of the original size.
Potential reduce by 10.5 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. Yway images are well optimized though.
Potential reduce by 563.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 563.8 kB or 65% of the original size.
Potential reduce by 74.9 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. Yway.ch needs all CSS files to be minified and compressed as it can save up to 74.9 kB or 82% of the original size.
Number of requests can be reduced by 60 (59%)
102
42
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yway. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
yway.ch
1302 ms
geocode_factory.css
203 ms
geocode_factory-maps_btn.css
309 ms
system.css
215 ms
general.css
210 ms
addons.css
213 ms
layout.css
395 ms
template.css
497 ms
joomla.css
600 ms
gk_stuff.css
502 ms
typo.css
607 ms
css3_style1.css
506 ms
style1.css
812 ms
jquery-min.js
1655 ms
js
25 ms
mootools.js
1036 ms
domready_fix.js
613 ms
gk.script.js
713 ms
markerclusterer.js
904 ms
map_api.js
1098 ms
parsexml.js
907 ms
index2.php
999 ms
mega.css
1100 ms
mega.js
1219 ms
stylesheet.css
1198 ms
show_ads.js
7 ms
common.js
42 ms
map.js
43 ms
layers.js
43 ms
util.js
44 ms
geocoder.js
41 ms
geometry.js
43 ms
poly.js
42 ms
ga.js
40 ms
bg_sus.jpg
303 ms
mc.png
221 ms
menu_sprite.png
200 ms
ca-pub-3230648763703324.js
150 ms
zrt_lookup.html
151 ms
show_ads_impl.js
82 ms
__utm.gif
74 ms
logo_yway.png
402 ms
infowindow.js
63 ms
ads
258 ms
__utm.gif
20 ms
osd.js
11 ms
connect.php
132 ms
410ucuAGgaJ.css
28 ms
q68gy-v_YMF.js
34 ms
8w-1WQE8wsO.js
54 ms
0wM5s1Khldu.js
67 ms
1bNoFZUdlYZ.js
53 ms
I6-MnjEovm5.js
10 ms
pQrUxxo5oQp.js
10 ms
m_js_controller.js
27 ms
abg.js
37 ms
favicon
41 ms
googlelogo_color_112x36dp.png
28 ms
nessie_icon_tiamat_white.png
24 ms
s
13 ms
x_button_blue2.png
5 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
68 ms
onion.js
43 ms
openhand_8_8.cur
36 ms
controls.js
26 ms
places_impl.js
25 ms
overlay.js
26 ms
icon_wait.gif
226 ms
imgs8.png
23 ms
arrow-down.png
83 ms
ViewportInfoService.GetViewportInfo
141 ms
stats.js
17 ms
ui
116 ms
css
61 ms
transparent.png
45 ms
powered-by-google-on-white3.png
45 ms
autocomplete-icons.png
46 ms
google4.png
63 ms
mapcnt6.png
63 ms
tmapctrl.png
45 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
41 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
41 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
42 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
41 ms
vt
81 ms
vt
101 ms
vt
26 ms
vt
25 ms
vt
23 ms
vt
66 ms
vt
25 ms
vt
86 ms
vt
25 ms
vt
26 ms
vt
26 ms
vt
28 ms
vt
27 ms
vt
75 ms
vt
28 ms
vt
29 ms
vt
32 ms
vt
79 ms
vt
55 ms
vt
58 ms
vt
62 ms
vt
121 ms
vt
64 ms
vt
67 ms
vt
68 ms
yway.ch 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
yway.ch best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
yway.ch SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yway.ch can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Yway.ch 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.
yway.ch
Open Graph description is not detected on the main page of Yway. 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: