Tools & Wizards About Us
felsentherme.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

felsentherme.com

Felsentherme Bad Gastein

Page Load Speed

3.4 sec in total

First Response

343 ms

Resources Loaded

2.7 sec

Page Rendered

319 ms

felsentherme.com screenshot

About Website

Click here to check amazing Felsentherme content for Austria. Otherwise, check out these important facts you probably never knew about felsentherme.com

Thermenurlaub in Bad Gastein dem Weltkulturort mit besonderem Flair.

Visit felsentherme.com

Key Findings

We analyzed Felsentherme.com page load time and found that the first response time was 343 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

felsentherme.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value12.5 s

0/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value250 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value1.531

0/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

felsentherme.com

343 ms

www.felsentherme.com

789 ms

stylesheet_53869674b1.css

98 ms

magnific-popup.css

193 ms

bootstrap.css

297 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 67% of them (40 requests) were addressed to the original Felsentherme.com, 8% (5 requests) were made to S7.addthis.com and 3% (2 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Felsentherme.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 991.8 kB (21%)

Content Size

4.7 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Felsentherme.com main page is 4.7 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 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 155.0 kB

  • Original 206.3 kB
  • After minification 203.6 kB
  • After compression 51.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 155.0 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 102.3 kB

  • Original 3.4 MB
  • After minification 3.3 MB

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. Felsentherme images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 579.1 kB

  • Original 858.3 kB
  • After minification 807.6 kB
  • After compression 279.3 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 579.1 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 155.4 kB

  • Original 185.1 kB
  • After minification 149.1 kB
  • After compression 29.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. Felsentherme.com needs all CSS files to be minified and compressed as it can save up to 155.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (46%)

Requests Now

57

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Felsentherme. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

felsentherme.com

felsentherme.com

343 ms

www.felsentherme.com

www.felsentherme.com

789 ms

stylesheet_53869674b1.css

stylesheet_53869674b1.css

98 ms

magnific-popup.css

magnific-popup.css

193 ms

bootstrap.css

bootstrap.css

297 ms

responsiveslides.css

responsiveslides.css

197 ms

owl.carousel.css

owl.carousel.css

198 ms

owl.theme.css

owl.theme.css

199 ms

felsentherme.css

felsentherme.css

199 ms

ke_search_pi1.css

ke_search_pi1.css

291 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

13 ms

jquery-ui.min.js

jquery-ui.min.js

18 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

401 ms

jquery.filter-isImageFile.min.js

jquery.filter-isImageFile.min.js

400 ms

bootstrap.js

bootstrap.js

405 ms

responsiveslides.js

responsiveslides.js

399 ms

owl.carousel.js

owl.carousel.js

410 ms

custom.js

custom.js

414 ms

ga.js

ga.js

412 ms

addthis_widget.js

addthis_widget.js

14 ms

conversion.js

conversion.js

20 ms

jquery-ui.css

jquery-ui.css

26 ms

ui.theme.css

ui.theme.css

32 ms

%7B$plugin.tx_powermail.settings.javascript.powermailJQuery%7D

%7B$plugin.tx_powermail.settings.javascript.powermailJQuery%7D

651 ms

powermail_frontend.js

powermail_frontend.js

404 ms

dc.js

dc.js

157 ms

132 ms

felsentherme_logo.png

felsentherme_logo.png

175 ms

header_2.jpg

header_2.jpg

550 ms

Felsentherme_Herzlichkeit.jpg

Felsentherme_Herzlichkeit.jpg

549 ms

header_gutscheinshop_std_01.jpg

header_gutscheinshop_std_01.jpg

537 ms

header_3.jpg

header_3.jpg

550 ms

Felsentherme_Herzlichkeit_Sauna.jpg

Felsentherme_Herzlichkeit_Sauna.jpg

550 ms

Bild_News.jpg

Bild_News.jpg

739 ms

csm_Felsentherme_Mitarbeiter_01_826ed7d13a.jpg

csm_Felsentherme_Mitarbeiter_01_826ed7d13a.jpg

548 ms

csm__MAX7701_ec876b06e1.jpg

csm__MAX7701_ec876b06e1.jpg

1021 ms

csm__MAX0044_2_75bb2fa993.jpg

csm__MAX0044_2_75bb2fa993.jpg

743 ms

csm_AlpinesLebensgefuehl_35c47d4c01.jpg

csm_AlpinesLebensgefuehl_35c47d4c01.jpg

733 ms

csm_Silberkrug_image1_SW_23bbd52b9f.jpg

csm_Silberkrug_image1_SW_23bbd52b9f.jpg

930 ms

csm_BadGastein_Reloaded_11aa07d8e1.jpg

csm_BadGastein_Reloaded_11aa07d8e1.jpg

824 ms

csm_HoheTauern_d8495946ac.jpg

csm_HoheTauern_d8495946ac.jpg

930 ms

anreise.jpg

anreise.jpg

832 ms

os_regular.woff

os_regular.woff

822 ms

sdk.js

sdk.js

80 ms

__utm.gif

__utm.gif

78 ms

171 ms

os_light.woff

os_light.woff

781 ms

os_semibold.woff

os_semibold.woff

790 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

791 ms

300lo.json

300lo.json

27 ms

counter.5524cceca805eb4b9b2b.js

counter.5524cceca805eb4b9b2b.js

17 ms

themes.gif

themes.gif

749 ms

blue85.png

blue85.png

754 ms

85 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

68 ms

shares.json

shares.json

50 ms

xd_arbiter.php

xd_arbiter.php

201 ms

xd_arbiter.php

xd_arbiter.php

259 ms

layers.e5ea973510bf60b3db41.js

layers.e5ea973510bf60b3db41.js

41 ms

de.js

de.js

26 ms

Accessibility Review

felsentherme.com accessibility score

87

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

felsentherme.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

felsentherme.com SEO score

93

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Felsentherme.com 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 Felsentherme.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.

Social Sharing Optimization

felsentherme.com

Open Graph description is not detected on the main page of Felsentherme. 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: