6.4 sec in total
1.5 sec
4.7 sec
192 ms
Visit taull.com now to see the best up-to-date Taull content and also check out these interesting facts you probably never knew about taull.com
Sitio Oficial Hotel Santa Maria de Taull
Visit taull.comWe analyzed Taull.com page load time and found that the first response time was 1.5 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
taull.com performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value6.1 s
12/100
25%
Value12.2 s
3/100
10%
Value5,510 ms
0/100
30%
Value0
100/100
15%
Value15.1 s
7/100
10%
1501 ms
83 ms
38 ms
167 ms
165 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 65% of them (41 requests) were addressed to the original Taull.com, 13% (8 requests) were made to Ruralgest.net and 5% (3 requests) were made to Tripadvisor.es. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Taull.com.
Page size can be reduced by 1.4 MB (61%)
2.2 MB
857.0 kB
In fact, the total size of Taull.com main page is 2.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. 40% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 29.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 29.4 kB or 78% 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. Taull images are well optimized though.
Potential reduce by 809.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 809.3 kB or 72% of the original size.
Potential reduce by 494.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. Taull.com needs all CSS files to be minified and compressed as it can save up to 494.9 kB or 85% of the original size.
Number of requests can be reduced by 46 (75%)
61
15
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Taull. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
www.taull.com
1501 ms
language-selector.css
83 ms
css
38 ms
social_widget.css
167 ms
style.css
165 ms
style.css
168 ms
font-awesome.min.css
193 ms
stylesheet.min.css
448 ms
style_dynamic.css
227 ms
responsive.min.css
247 ms
style_dynamic_responsive.css
246 ms
js_composer.css
330 ms
custom_css.css
290 ms
style.css
327 ms
jquery.js
470 ms
jquery-migrate.min.js
384 ms
html5.js
410 ms
uk-cookie-consent-js.js
413 ms
qode-like.js
470 ms
plugins.js
1023 ms
jquery.carouFredSel-6.2.1.min.js
570 ms
lemmon-slider.min.js
494 ms
jquery.fullPage.min.js
558 ms
jquery.mousewheel.min.js
528 ms
jquery.touchSwipe.min.js
569 ms
isotope.pkgd.min.js
577 ms
js
47 ms
default_dynamic.js
609 ms
default.min.js
672 ms
custom_js.js
678 ms
comment-reply.min.js
650 ms
js_composer_front.js
660 ms
wp-embed.min.js
690 ms
sitepress.js
732 ms
ext_v001.php
558 ms
wp-emoji-release.min.js
654 ms
wejs
406 ms
style.css
467 ms
logo-300.png
339 ms
DSC_2962-e1446668090811.jpg
340 ms
IMG_2401-e1447660791447.jpg
340 ms
jarra-bretona-e1446719249771.jpg
337 ms
logocolor.png
503 ms
iconos-ok1.png
375 ms
iconos-foofter.png
512 ms
ga.js
10 ms
WidgetEmbed-cdsratingsonlynarrow
46 ms
__utm.gif
17 ms
tripadvisor_logo_transp_340x80-18034-2.png
22 ms
d93e757e1104.png
6 ms
cdswidget-ratingsonly-v21719610117a.css%20%27%29%3B
6 ms
cdswidgets_m-c-v2102084671a.js
25 ms
cdswidget-ratingsonly-v21719610117a.css
21 ms
cf5f02a7dec1.png
25 ms
jquery-1.7.2.min.js
323 ms
jquery-ui-1.8.20.custom.css
232 ms
widget.css
158 ms
dd.css
162 ms
estilos_widget.css
163 ms
TCalendarioDisponibilidadJQ.css
164 ms
CSS_TSimpleSearch.php
272 ms
4.5.png
24 ms
tripadvisor_logo_transp_340x80-18034-2.png
25 ms
taull.com accessibility score
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
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.
taull.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
taull.com SEO score
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
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Taull.com can be misinterpreted by Google and other search engines. Our service has detected that Catalan is used on the page, and it does not match the claimed Spanish language. Our system also found out that Taull.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.
taull.com
Open Graph description is not detected on the main page of Taull. 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: