4.5 sec in total
1.1 sec
3.3 sec
119 ms
Click here to check amazing Rosamar content. Otherwise, check out these important facts you probably never knew about rosamar.com
Hotel Rosamar situat a primera línia de mar a Sant Antoni de Calonge, a la Costa Brava. Vistes privilegiades a la badia i accés al cami de ronda de la Costa.
Visit rosamar.comWe analyzed Rosamar.com page load time and found that the first response time was 1.1 sec and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
rosamar.com performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value62.6 s
0/100
25%
Value69.6 s
0/100
10%
Value180 ms
92/100
30%
Value1.002
2/100
15%
Value92.4 s
0/100
10%
1122 ms
112 ms
208 ms
209 ms
207 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 73% of them (70 requests) were addressed to the original Rosamar.com, 6% (6 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Rosa_mar.web-reservations.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Rosamar.com.
Page size can be reduced by 1.6 MB (50%)
3.2 MB
1.6 MB
In fact, the total size of Rosamar.com main page is 3.2 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. 65% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 36.9 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 36.9 kB or 82% of the original size.
Potential reduce by 26.0 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. Rosamar images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 80% of the original size.
Potential reduce by 431.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. Rosamar.com needs all CSS files to be minified and compressed as it can save up to 431.6 kB or 84% of the original size.
Number of requests can be reduced by 69 (79%)
87
18
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rosamar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 34 to 1 for CSS and as a result speed up the page load time.
rosamar.com
1122 ms
language-selector.css
112 ms
ultimate-tables.css
208 ms
reset.min.css
209 ms
jquery.fancybox.min.css
207 ms
style.css
219 ms
estilos.css
222 ms
awesome-weather.css
243 ms
css
70 ms
style2-os.css
307 ms
lightbox.css
306 ms
style.css
328 ms
bootstrap.min.css
441 ms
owl.carousel.css
361 ms
royalslider.css
405 ms
rs-default.css
407 ms
stylesheet.css
411 ms
font-awesome.min.css
435 ms
style.css
481 ms
bootstrap-select.css
506 ms
comments.css
508 ms
jquery.datetimepicker.css
510 ms
shortcodes.css
545 ms
animate.css
551 ms
jquery.mCustomScrollbar.css
603 ms
um_widgets.css
607 ms
global.css
610 ms
main_stylesheet.css
611 ms
css
39 ms
css
51 ms
jquery.js
764 ms
jquery-migrate.min.js
659 ms
principal.js
721 ms
jquery.dataTables.js
1012 ms
jquery.ck.min.js
707 ms
ninjapopups.min.js
713 ms
jquery.fancybox.min.js
767 ms
jquery.colorbox.js
810 ms
js
84 ms
gallery-all.js
813 ms
jquery.hugeitmicro.min.js
743 ms
jquery.easing-1.3.js
679 ms
jquery.royalslider.min.js
684 ms
owl.carousel.js
719 ms
jquery.scrolly.js
709 ms
jquery.smoothscroll.js
753 ms
bootstrap.min.js
754 ms
bootstrap-select.js
697 ms
isotope.js
724 ms
imagesloaded.pkgd.min.js
724 ms
main_stylesheet.css
772 ms
jquery.datetimepicker.js
784 ms
jquery.mCustomScrollbar.min.js
740 ms
jquery.twitterfeed.js
737 ms
tabAccTog.js
735 ms
main_script.js
708 ms
rooms_script.js
782 ms
um_booking.js
750 ms
um_lightbox.js
726 ms
comment-reply.min.js
724 ms
sitepress.js
723 ms
roomsearchersearchbox
56 ms
wifi_bar.png
199 ms
logo_1002.png
206 ms
preu_cat2.png
449 ms
hotel_slide.jpg
1002 ms
terrassa_slide.jpg
594 ms
bahia_slide.jpg
824 ms
posta_slide.jpg
756 ms
bahia2_slide.jpg
875 ms
IczWvq5y_Cwwv_rBjOtT0w.woff
36 ms
fontawesome-webfont.woff
792 ms
roomsearchersearchbox
448 ms
fancybox_overlay.png
549 ms
input-email.png
602 ms
preloader-white.gif
658 ms
close_3.png
508 ms
1abd024.css
107 ms
eb3277f.css
93 ms
css
55 ms
styles-20.css
164 ms
5c0ead2.js
114 ms
b041f0d.js
120 ms
a767fb9.js
97 ms
routing
209 ms
en
208 ms
sprite.png
41 ms
ui-bg_flat_75_ffffff_40x100.png
14 ms
btn_calendar.gif
13 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
8 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
7 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
8 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
8 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
10 ms
nr-892.min.js
98 ms
39555a2462
117 ms
rosamar.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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
rosamar.com 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
rosamar.com 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
CA
CA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rosamar.com can be misinterpreted by Google and other search engines. Our service has detected that Catalan is used on the page, and it matches the claimed language. Our system also found out that Rosamar.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.
rosamar.com
Open Graph description is not detected on the main page of Rosamar. 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: