4.3 sec in total
207 ms
3.4 sec
641 ms
Click here to check amazing BARRY content. Otherwise, check out these important facts you probably never knew about barry.at
Urlaub in Kärnten Seeappartements Ferienwohnungen in Velden am Wörthersee. Direkt am See im Hotel BARRY MEMLE - laufend aktuelle Packages Last-minute buchen
Visit barry.atWe analyzed Barry.at page load time and found that the first response time was 207 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.
barry.at performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value14.2 s
0/100
25%
Value5.2 s
59/100
10%
Value10 ms
100/100
30%
Value0.638
9/100
15%
Value4.6 s
81/100
10%
207 ms
625 ms
217 ms
512 ms
303 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 88% of them (60 requests) were addressed to the original Barry.at, 6% (4 requests) were made to Maps.googleapis.com and 3% (2 requests) were made to Player.vimeo.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Barry.at.
Page size can be reduced by 122.6 kB (1%)
11.7 MB
11.6 MB
In fact, the total size of Barry.at main page is 11.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. 45% of websites need less resources to load. Images take 11.3 MB which makes up the majority of the site volume.
Potential reduce by 63.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 63.4 kB or 80% of the original size.
Potential reduce by 3.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. BARRY images are well optimized though.
Potential reduce by 52.4 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 52.4 kB or 18% of the original size.
Potential reduce by 3.2 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. Barry.at has all CSS files already compressed.
Number of requests can be reduced by 13 (20%)
65
52
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of BARRY. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
barry.at
207 ms
barry.at
625 ms
bundle.css
217 ms
bundle.js
512 ms
webfont-local.js
303 ms
scripte.js
300 ms
jquery-ui.js
605 ms
jquery.ui.datepicker-lang.js
312 ms
jquery-ui.css
323 ms
player.js
39 ms
zp-webfonts.css
106 ms
hg_entwurf.jpg
212 ms
icon-booking.png
102 ms
icon-enquiry.png
103 ms
icon-reservation.png
102 ms
icon-calc.png
105 ms
icon-telefon.png
102 ms
icon-whatsapp.png
202 ms
logo.png
399 ms
logo-klein-d.png
203 ms
home_01-large.jpg
401 ms
home_02-large.jpg
936 ms
home_03-large.jpg
797 ms
home_04-large.jpg
503 ms
home_05-large.jpg
1463 ms
home_06-large.jpg
797 ms
home_07-large.jpg
701 ms
home_08-large.jpg
607 ms
home_09-large.jpg
1209 ms
home_10-large.jpg
808 ms
home_11-large.jpg
905 ms
home_12-large.jpg
998 ms
unter.png
908 ms
herbst01_45_d.jpg
1007 ms
wellness01_45_d.jpg
1008 ms
home-terrasse04.jpg
1040 ms
home-terrasse02.jpg
1097 ms
home-terrasse05.jpg
1110 ms
home-terrasse03.jpg
1110 ms
home-wellness01.jpg
1144 ms
home-wellness03.jpg
1200 ms
home-wellness02.jpg
1211 ms
home-wellness04.jpg
1211 ms
tripadvisor.png
1249 ms
holidaycheck.jpg
1299 ms
zoover.jpg
1306 ms
booking.png
1297 ms
901254186
141 ms
embed
357 ms
hrs.png
1213 ms
kajak.jpg
1255 ms
hotel-de.jpg
1302 ms
logo-bed-bike.jpg
1307 ms
ktn_beherbergung.png
1310 ms
api.js
9 ms
ktn_best_price_garantie.png
1213 ms
footer-large.jpg
1756 ms
logo-instagram.png
1294 ms
logo-facebook.png
1111 ms
parallax_home01-large.jpg
1114 ms
js
29 ms
search.js
4 ms
geometry.js
7 ms
main.js
13 ms
parallax_home02-large.jpg
1012 ms
ul_icon.png
960 ms
parallax_home04-large.jpg
908 ms
bundle-print.css
107 ms
barry.at 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Links do not have a discernible name
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
barry.at 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
General
Impact
Issue
Detected JavaScript libraries
barry.at 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
![]()
DE
![]()
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Barry.at 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 Barry.at 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.
barry.at
Open Graph data is detected on the main page of BARRY. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: