12.9 sec in total
231 ms
11.6 sec
1.1 sec
Click here to check amazing Frankenbourg content. Otherwise, check out these important facts you probably never knew about frankenbourg.com
Site Officiel ✅ Meilleur Tarif en Direct : Hôtel et auberge de charme avec restaurant gastronomique étoilé, situé au cœur de l'Alsace à la Vancelle.
Visit frankenbourg.comWe analyzed Frankenbourg.com page load time and found that the first response time was 231 ms and then it took 12.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
frankenbourg.com performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value18.0 s
0/100
25%
Value26.9 s
0/100
10%
Value4,790 ms
0/100
30%
Value0
100/100
15%
Value23.3 s
1/100
10%
231 ms
4295 ms
642 ms
216 ms
669 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 79% of them (97 requests) were addressed to the original Frankenbourg.com, 12% (15 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Dev.hotelsmartwidgets.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Frankenbourg.com.
Page size can be reduced by 113.3 kB (2%)
5.4 MB
5.3 MB
In fact, the total size of Frankenbourg.com main page is 5.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. 70% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.
Potential reduce by 103.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 103.4 kB or 83% of the original size.
Potential reduce by 508 B
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. Frankenbourg images are well optimized though.
Potential reduce by 7.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. This website has mostly compressed JavaScripts.
Potential reduce by 1.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. Frankenbourg.com has all CSS files already compressed.
Number of requests can be reduced by 53 (50%)
105
52
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frankenbourg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
frankenbourg.com
231 ms
4295 ms
hsw-frankenbourg.css
642 ms
style.min.css
216 ms
light-box-styles.css
669 ms
swiper.min.css
322 ms
orejime.css
580 ms
flatpickr.min.css
668 ms
wppopups-base.css
341 ms
style.min.css
431 ms
style.min.css
456 ms
style.min.css
539 ms
css
35 ms
style-static.min.css
811 ms
style.css
645 ms
jquery.min.js
1201 ms
jquery-migrate.min.js
775 ms
flatpickr.min.js
780 ms
all.js
890 ms
et-core-unified-tb-1921-tb-778-464.min.css
894 ms
et-core-unified-464.min.css
923 ms
style.min.css
899 ms
style.min.css
906 ms
style.min.css
937 ms
mediaelementplayer-legacy.min.css
1009 ms
wp-mediaelement.min.css
1015 ms
regenerator-runtime.min.js
1051 ms
wp-polyfill.min.js
1467 ms
hooks.min.js
1165 ms
wppopups.js
1236 ms
swiper.min.js
1246 ms
orejime.js
706 ms
effect.min.js
1563 ms
scripts.min.js
1631 ms
smoothscroll.js
1976 ms
es6-promise.auto.min.js
1352 ms
api.js
39 ms
recaptcha.js
1456 ms
jquery.fitvids.js
1566 ms
comment-reply.min.js
1571 ms
jquery.mobile.js
1575 ms
magnific-popup.js
1671 ms
hsw-frankenbourg.js
802 ms
easypiechart.js
1673 ms
salvattore.js
1566 ms
frontend-bundle.min.js
1467 ms
frontend-bundle.min.js
1507 ms
frontend-bundle.min.js
1456 ms
common.js
1433 ms
dipl-modal-custom.min.js
1354 ms
dipl-button-custom.min.js
1252 ms
mediaelement-and-player.min.js
1762 ms
mediaelement-migrate.min.js
1329 ms
wp-mediaelement.min.js
1236 ms
motion-effects.js
1339 ms
sticky-elements.js
1398 ms
gtm.js
174 ms
texture_bg_01.png
889 ms
logo_white_v2.svg
890 ms
guide_michelin_blanc-2.svg
960 ms
guide_michelin_colors-3.svg
982 ms
logis_white.svg
1343 ms
Guillaume-Buecher-x-chambre-121.jpg
1861 ms
Guillaume-Buecher-x-chambre-75.jpg
1342 ms
Guillaume-Buecher-x-chambre-101.jpg
1342 ms
Guillaume-Buecher-x-chambre-101-bis.jpg
1345 ms
727367360
296 ms
Guillaume-Buecher-x-cuisine-6.jpg
1502 ms
icon-diadao.png
1356 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff
22 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff
32 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff
51 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aXw.woff
59 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aXw.woff
59 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff
61 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff
61 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff
63 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aXw.woff
60 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDZbtU.woff
61 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDZbtU.woff
61 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDZbtU.woff
112 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDZbtU.woff
112 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfFunDZbtU.woff
113 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDZbtU.woff
113 ms
modules.ttf
1351 ms
maitre_restaurateur.svg
1350 ms
label-qualite-tourisme.png
1221 ms
1464265207-0816898ed530ec2a11f9d47f936c975ea2b653f59eafd9999137de2ea9c4c25d-d
58 ms
table_distingueee.png
1196 ms
logis_white-1.svg
1169 ms
menu_icon_brown-1.svg
1105 ms
Guillaume-Buecher-x-nature-et-verger-21.jpg
1115 ms
close_icon_brown.svg
1195 ms
calendar_icon_brown_40px.svg
1192 ms
preloader.gif
1109 ms
Guillaume-Buecher-x-chambre-117.jpg
1430 ms
V2-Montage-Colo-1.00_00_47_44810.Still027-1.jpg
1114 ms
Guillaume-Buecher-x-chambre-102.jpg
1202 ms
texture_bg_01-1.png
1192 ms
Guillaume-Buecher-x-nature-et-verger.jpg
1374 ms
Guillaume-Buecher-x-cuisine-5.jpg
1120 ms
Guillaume-Buecher-x-nature-et-verger-1.jpg
1202 ms
Guillaume-Buecher-x-cuisine-2.jpg
1320 ms
Guillaume-Buecher-x-nature-et-verger-3.jpg
1221 ms
Guillaume-Buecher-x-cuisine-7-scaled.jpg
1320 ms
Guillaume-Buecher-x-nature-et-verger-15.jpg
1407 ms
Guillaume-Buecher-x-nature-et-verger-8-DARKER.jpg
1109 ms
ElodieWinter_Frankenbourg_mars2021-35-scaled.jpg
1740 ms
ElodieWinter_Frankenbourg_mars2021-40-scaled.jpg
1207 ms
Guillaume-Buecher-coucou-9.jpg
1435 ms
ElodieWinter_Frankenbourg_mars2021-34-scaled.jpg
1145 ms
Guillaume-Buecher-x-cuisne-1-scaled.jpg
1207 ms
Guillaume-Buecher-x-cuisine--scaled.jpg
1312 ms
Guillaume-Buecher-x-nature-et-verger-9-scaled.jpg
1065 ms
727367360
143 ms
chateau_2.jpg
1491 ms
chateau_1.jpg
958 ms
chateau_3.jpg
1178 ms
subscribe-loader.gif
996 ms
Guillaume-Buecher-x-nature-et-verger-20.jpg
980 ms
1464265207-0816898ed530ec2a11f9d47f936c975ea2b653f59eafd9999137de2ea9c4c25d-d
23 ms
up_icon_brown.svg
978 ms
down_icon_brown.svg
1088 ms
frankenbourg.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
frankenbourg.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
frankenbourg.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frankenbourg.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed French language. Our system also found out that Frankenbourg.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.
frankenbourg.com
Open Graph data is detected on the main page of Frankenbourg. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: