4.9 sec in total
463 ms
4.1 sec
322 ms
Click here to check amazing Falstaff content for Switzerland. Otherwise, check out these important facts you probably never knew about falstaff.ch
Das Genuss-Medium. Mit über 100.000 Wein-Bewertungen, Restaurants, Reisen, Cocktails und den besten Rezepten zum Nachkochen.
Visit falstaff.chWe analyzed Falstaff.ch page load time and found that the first response time was 463 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
falstaff.ch performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value23.1 s
0/100
25%
Value11.2 s
5/100
10%
Value3,160 ms
2/100
30%
Value0.025
100/100
15%
Value17.1 s
4/100
10%
463 ms
1022 ms
196 ms
532 ms
369 ms
Our browser made a total of 138 requests to load all elements on the main page. We found that 48% of them (66 requests) were addressed to the original Falstaff.ch, 11% (15 requests) were made to Static.xx.fbcdn.net and 9% (12 requests) were made to Ad1.adfarm1.adition.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Falstaff.ch.
Page size can be reduced by 439.7 kB (38%)
1.1 MB
702.8 kB
In fact, the total size of Falstaff.ch main page is 1.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. 70% of websites need less resources to load. Images take 533.4 kB which makes up the majority of the site volume.
Potential reduce by 71.4 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 71.4 kB or 77% of the original size.
Potential reduce by 42.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. Falstaff images are well optimized though.
Potential reduce by 211.7 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 211.7 kB or 55% of the original size.
Potential reduce by 114.1 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. Falstaff.ch needs all CSS files to be minified and compressed as it can save up to 114.1 kB or 87% of the original size.
Number of requests can be reduced by 68 (51%)
134
66
The browser has sent 134 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Falstaff. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
falstaff.ch
463 ms
www.falstaff.ch
1022 ms
stylesheet_888b19f7d0.css
196 ms
home.css,slidermain.css,twitter.css,felogin.css,comments.css,community_tx_srfeuserregister.css,blog.css,myquizpoll.css,search.css,fgc_restaurants.css,rte.css,menu_nws.css,advent.css
532 ms
ch_overload.css
369 ms
solr_results.css
374 ms
styles_min.css
379 ms
jquery-ui.custom.css
377 ms
adition.js
369 ms
js
277 ms
js
279 ms
js
282 ms
js
278 ms
js
281 ms
js
283 ms
jquery.min.js
33 ms
hoverIntent_orig.js,superfish_orig.js,common_de.js,search.js,slidermain_de.js,comments.js,jquery.xml2json.pack.js,jquery.imagemapster.js,advent.js
583 ms
jquery.twitter-friends-1.0.min.js
60 ms
jquery-ui.core.min.js
553 ms
jquery-ui.autocomplete.min.js
557 ms
suggest.js
1017 ms
results.js
565 ms
jquery.cycle.all.js
21 ms
falstaffBig.gif
185 ms
1df3276024.jpg
215 ms
Baltho-468.jpg
411 ms
DSCN0598-c-Falstaff-195_01.jpg
226 ms
schiefergestein-Weinberg-c-weingut-meyer-naekel-dieth-195_01.jpg
247 ms
BottleParty_018-c-KristinGuenther-195_01.jpg
376 ms
TheViewSkybar-beigestellt-195.jpg
394 ms
wein_am_berg_2016_bottles-195_01.jpg
601 ms
ivan-barbic-jan-schwarzenbach-195.jpg
482 ms
40000_FB_Fans_Pommery_195_02.jpg
569 ms
WT16-Gewinner-VictoriaLergenmueller-ErnieLoosen-NinaMann-TheresaBreuer-PeterJakobKuehn-20160226fW_282-c-AloisMueller-195_02.jpg
583 ms
WP-Team-195_01.jpg
594 ms
Steirereck-neu-PR-195_02.jpg
653 ms
Restaurant-Saltz-c-Nico-Schaerer-195.jpg
667 ms
Hummer-rezeptstrecke-c-stefan-liewehr-195.jpg
731 ms
dominique-krenn-c-helge-kirchberger-195_01.jpg
753 ms
hummer-china-shutterstock-195.jpg
771 ms
Schiffchen-beigestellt-195_01.jpg
798 ms
AdiWerner_c-THomas-Schauer-195_02.jpg
1015 ms
einstein-195.jpg
853 ms
genussmythen_195_01.jpg
908 ms
BurgerTopTenKoeln-FetteKuh-beigestellt-195_01.jpg
936 ms
Grand-Ferdinand-zimmer-195_01.jpg
958 ms
Cafeatery-c-StevanPaul-195_02.jpg
981 ms
Alohacherie-Hamburg-SeitanRagout-getrueffeltesKuerbispueree-SteinpilzeInRotweinjus-Gojibeeren-195_01.jpg
1056 ms
editors-choice-Sexy-Fish-c-Paul-Winch-Furness-195_01.jpg
1084 ms
The-Palm-Towers-rooftop-c-beigestellt-195_01.jpg
1133 ms
special-marktplatz-shutterstock-195_01.jpg
1141 ms
das-schaefer-195_01.jpg
1164 ms
The-Boilerman-Bar-Hamburg-The-Backbar-c-BigShrimp-195_02.jpg
1242 ms
banner
178 ms
uid.html
92 ms
shutterstock_Ostereier-195.jpg
1273 ms
csm_el_laguito_cohiba_factory-195.jpg
1269 ms
Feuerring-leidenschaftliche-c-beigestellt-195_01.jpg
1306 ms
Interview-Hoejsgaard-PR-195_01.jpg
1305 ms
Chefs-Edition-Davidoff-195_01.jpg
1310 ms
davidoff-escurio-195_01.jpg
1241 ms
000000663610.jpg
175 ms
banner
177 ms
top10bars-zuerich-old-crow--beigestelt-195.jpg
1230 ms
Davidoff-moodbox-beigestellt-195.jpg
1267 ms
Davidoff-pfeife_tob_45_195.jpg
1372 ms
sucheButton.gif
1242 ms
000000660144.gif
110 ms
sdk.js
16 ms
plusone.js
85 ms
bgTop.png
1226 ms
banner
185 ms
bgMiddle.png
1188 ms
72 ms
xd_arbiter.php
34 ms
xd_arbiter.php
63 ms
aktuell_bg_new.png
1150 ms
cb=gapi.loaded_0
15 ms
cb=gapi.loaded_1
14 ms
fastbutton
69 ms
diashowIcon.png
1143 ms
postmessageRelay
53 ms
cb=gapi.loaded_0
26 ms
cb=gapi.loaded_1
26 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
61 ms
advertorial.png
1132 ms
000000619373.jpg
99 ms
banner
180 ms
3193398744-postmessagerelay.js
35 ms
rpc:shindig_random.js
39 ms
cb=gapi.loaded_0
3 ms
banner
175 ms
bgBottom.png
762 ms
banner
172 ms
clickurl=;ord=6263825483250139223
50 ms
html_inpage_rendering_lib_200_120.js
66 ms
gtm.js
67 ms
inactiveCar.gif
564 ms
backward.gif
575 ms
forward.gif
580 ms
activeCar.gif
575 ms
ui-bg_highlight-hard_100_f7f7f7_1x100.png
638 ms
analytics.js
24 ms
fbevents.js
21 ms
page.php
141 ms
300x600_de_Coop_Mondovino_Burgund_2016_01.jpg
44 ms
dc_oe=ChMIlJm_x6rNywIVQwg3Ch12YQHUEAAYACDmgvYg;met=1;×tamp=1458410519368;eid1=9;ecn1=1;etm1=0;
17 ms
lidar.js
15 ms
collect
8 ms
collect
50 ms
9 ms
LUdypCgtRlc.css
34 ms
Hy2B8ciSPhU.css
41 ms
q68gy-v_YMF.js
44 ms
YvxwM8R7ol8.js
62 ms
ihptErjAmMX.js
61 ms
1BQnIVjTFoC.js
60 ms
6PDLJFN-l6_.js
82 ms
cUsKAwzqrQw.js
88 ms
10371461_10153624008550674_5575926617066465218_n.jpg
111 ms
10352609_10153629228885674_7031680169980399714_n.jpg
18 ms
11707527_862537817114861_1173538500157863461_n.jpg
21 ms
12661893_1180883918596966_8546462848983426373_n.jpg
22 ms
12524268_763846573748842_689491968966380592_n.jpg
22 ms
12376192_1018298678212546_5187101891748001954_n.jpg
132 ms
12308274_963784353683940_4690714964311607172_n.jpg
136 ms
940805_144232435950617_1738386331463833567_n.jpg
83 ms
12642830_10205672769247708_8594987940597173993_n.jpg
21 ms
wL6VQj7Ab77.png
13 ms
s7jcwEQH7Sx.png
13 ms
6GqoI2ZyIrf.png
14 ms
aktuell_bg_new.png
270 ms
R9a_DtVRZgv.js
5 ms
cUDgRFxaoIk.js
4 ms
0JBr1QHp8Gi.js
5 ms
kDOzhTr2W91.js
7 ms
print.css
186 ms
chartbeat.js
20 ms
falstaff.ch 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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
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.
[aria-*] attributes do not have valid values
ARIA IDs are not unique
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
falstaff.ch 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
falstaff.ch 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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Falstaff.ch can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Falstaff.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.
falstaff.ch
Open Graph description is not detected on the main page of Falstaff. 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: