Access petitpalace.com. Petit Palace Hotels · Hoteles boutique & modernos

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value13.3 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value1,510 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value13.3 s

12/100

10%

petitpalace.com

499 ms

www.petitpalace.com

1381 ms

font-awesome.min.css

283 ms

jquery.fancybox.min.css

195 ms

jquery-ui-1.10.3.custom.min.css

220 ms

Our browser made a total of 134 requests to load all elements on the main page. We found that 56% of them (75 requests) were addressed to the original Petitpalace.com, 3% (4 requests) were made to Config1.veinteractive.com and 3% (4 requests) were made to P.rfihub.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Petitpalace.com.

Content Size

2.5 MB

After Optimization

1.6 MB

In fact, the total size of Petitpalace.com main page is 2.5 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. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 93.4 kB

Original 111.6 kB
After minification 103.0 kB
After compression 18.2 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 93.4 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 29.9 kB

Original 1.3 MB
After minification 1.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. Petit Palace images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 617.5 kB

Original 844.9 kB
After minification 624.7 kB
After compression 227.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 617.5 kB or 73% of the original size.

CSS Optimization

-85%

Potential reduce by 166.6 kB

Original 197.2 kB
After minification 167.9 kB
After compression 30.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. Petitpalace.com needs all CSS files to be minified and compressed as it can save up to 166.6 kB or 85% of the original size.

Requests Now

121

After Optimization

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

Accessibility Issues

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.

High

button, link, and menuitem elements do not have accessible names.

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.

High

Buttons do not have an accessible name

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

ES
Language Claimed

ES
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Petitpalace.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Petitpalace.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

petitpalace.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Petit Palace Hotels · Hoteles boutique & modernos

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

petitpalace.com

www.petitpalace.com

font-awesome.min.css

jquery.fancybox.min.css

jquery-ui-1.10.3.custom.min.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

petitpalace.com

www.petitpalace.com

font-awesome.min.css

jquery.fancybox.min.css

jquery-ui-1.10.3.custom.min.css

ofertas.new.css

css

css

styles.css

modernizr.min.js

less-1.3.3.min.js

jquery.min.js

jquery-ui.min.js

jquery.easing.1.3.min.js

jquery.cookie.min.js

jquery.easytabs.min.js

jquery.fancybox.pack.js

general.min.js

jquery.carritotop.min.js

jquery.ui.datepicker-es.js

jquery.motorform_corp.min.js

jquery.newsletter.min.js

jquery.cookiesdirective.min.js

ld.js

jquery.bxslider.min.js

tag.js

conversion.js

ga.js

fondo_header.jpg

wifi.png

officialwebsite.png

logotipo-petit-palace-web_2.png

phone.png

flags.png

c6766aff961700b80f9e9c788e979d32.jpg

f77b4c73e384cd2bbed03539dd9cba1e.jpg

fc52febebe78cf76ccf1379e4aed4c99.jpg

f269657e78aad58e29b1973b65276a8c.jpg

ed4c30cd7f12659bf8e81d5fe0e0cd05.jpg

f39d07b26d8b0034b57afd231fe6ed30.jpg

749e3ba8d4869331885e04c85088a715.jpg

301be80638f6cb0a5e61be99f62aa084.jpg

adddea7ec9a71e5eafcda62aa33ba265.jpg