5 sec in total
400 ms
4 sec
584 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 400 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
barry.at performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value7.7 s
3/100
25%
Value4.9 s
64/100
10%
Value150 ms
95/100
30%
Value0.028
100/100
15%
Value6.6 s
57/100
10%
400 ms
117 ms
231 ms
229 ms
352 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 86% of them (78 requests) were addressed to the original Barry.at, 4% (4 requests) were made to Static.tacdn.com and 2% (2 requests) were made to Schmauzer.at. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Barry.at.
Page size can be reduced by 456.7 kB (15%)
3.1 MB
2.7 MB
In fact, the total size of Barry.at main page is 3.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. 60% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 35.6 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. This page needs HTML code to be minified as it can gain 10.7 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 35.6 kB or 81% of the original size.
Potential reduce by 49.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. BARRY images are well optimized though.
Potential reduce by 348.0 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 348.0 kB or 77% of the original size.
Potential reduce by 23.6 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 needs all CSS files to be minified and compressed as it can save up to 23.6 kB or 79% of the original size.
Number of requests can be reduced by 22 (25%)
88
66
The browser has sent 88 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 16 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
barry.at
400 ms
jquery.js
117 ms
jquery.lightbox-0.5.js
231 ms
scripte.js
229 ms
datepicker.js
352 ms
demo.css
234 ms
datepicker.css
233 ms
navi.css
238 ms
supersized.css
345 ms
supersized.shutter.css
348 ms
jquery.lightbox.css
349 ms
Schriften.css
348 ms
jquery-1.7.2.min.js
486 ms
jquery.easing.min.js
480 ms
supersized.3.2.7.min.js
484 ms
supersized.shutter.min.js
484 ms
jquery.lightbox-2.5.1.js
483 ms
jquery.cycle.all.js
507 ms
wejs
198 ms
snippet.php
302 ms
de.js
330 ms
icon_1.png
349 ms
Stacked_TA_logo.png
62 ms
icon_3.png
346 ms
schatten.png
134 ms
logo.png
597 ms
ger_kl.gif
135 ms
eng_kl1.gif
131 ms
ita_kl1.gif
136 ms
balken_D.jpg
138 ms
prev.png
266 ms
next.png
266 ms
pause.png
269 ms
start.png
271 ms
home1.jpg
1478 ms
home2.jpg
838 ms
home3.jpg
1625 ms
home4.jpg
1154 ms
home5.jpg
992 ms
home6.jpg
1091 ms
home7.jpg
1127 ms
home8.jpg
1262 ms
home9.jpg
1361 ms
trans_hg_content.png
1268 ms
trans_kaesten_breit.png
1285 ms
App_austria_1.jpg
1385 ms
App_austria_2.jpg
1394 ms
App_austria_3.jpg
1413 ms
trans_angebote.png
1483 ms
fruehling01_35_d.jpg
1512 ms
wellness01_35_d.jpg
1521 ms
trans_rechts.png
1540 ms
preiskalkulator_D.png
1581 ms
bewerten_D.gif
1593 ms
tripadvisor.png
1629 ms
holidaycheck.jpg
1638 ms
zoover.png
1654 ms
booking-com.jpg
1686 ms
hrs.jpg
1697 ms
WidgetEmbed-cdsscrollingravewide
293 ms
venere.jpg
1689 ms
index.php
357 ms
hotel-de.jpg
1628 ms
ktn_beherbergung.png
1643 ms
ktn_best_price_garantie.png
1669 ms
cdswidget-scrollingrave-v2823050010a.css%20%27%29%3B
3 ms
cdswidgets_min-c-v23892882724a.js
156 ms
cdswidget-scrollingrave-v2823050010a.css
153 ms
ga.js
452 ms
loading.gif
148 ms
close.png
232 ms
trans_hg_foot.png
1259 ms
progress.gif
1270 ms
home01.jpg
1721 ms
__utm.gif
56 ms
Stacked_TA_logo.png
47 ms
transparent_pixel-17198-2.gif
53 ms
detail1.gif
135 ms
ger_kl1.gif
136 ms
eng_kl.gif
131 ms
ita_kl.gif
132 ms
Tripadvisor.jpg
133 ms
HolidayCheck.jpg
258 ms
Zoover.jpg
369 ms
booking-com.jpg
249 ms
hrs.jpg
254 ms
venere.jpg
254 ms
Hotel_de.jpg
264 ms
Qualitaet.jpg
660 ms
Best_Price.jpg
520 ms
K_Symbol_grau15x17.png
382 ms
barry.at accessibility score
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
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
Tap targets are not sized appropriately
DE
N/A
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 neither this language nor any other was claimed in <html> or <meta> tags. 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 description is not detected on the main page of BARRY. 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: