Tools & Wizards About Us
ixtapapalaceresort.com screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

ixtapapalaceresort.com

Warning: Undefined variable $title in /home/week/public_html/iprx/inc/header.php on line 52 | Ixtapa Palace Resort & Spa

Page Load Speed

3.3 sec in total

First Response

114 ms

Resources Loaded

2.5 sec

Page Rendered

715 ms

ixtapapalaceresort.com screenshot

About Website

Click here to check amazing Ixtapa Palace Resort content. Otherwise, check out these important facts you probably never knew about ixtapapalaceresort.com

A distinctive hotel to relax and enjoy the tropical surroundings of Ixtapa Zihuatanejo, walking distance from beach.

Visit ixtapapalaceresort.com

Key Findings

We analyzed Ixtapapalaceresort.com page load time and found that the first response time was 114 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

ixtapapalaceresort.com performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value7,580 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.611

10/100

15%

TTI (Time to Interactive)

Value25.4 s

0/100

10%

Network Requests Diagram

ixtapapalaceresort.com

114 ms

www.ixtapapalaceresort.com

112 ms

www.ixtapapalaceresort.com

253 ms

css

40 ms

bootstrap.min.css

207 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 63% of them (67 requests) were addressed to the original Ixtapapalaceresort.com, 14% (15 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Ixtapapalaceresort.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.3 MB (28%)

Content Size

11.9 MB

After Optimization

8.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ixtapapalaceresort.com main page is 11.9 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. Only a small number of websites need less resources to load. Images take 10.7 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 37.2 kB

  • Original 45.3 kB
  • After minification 33.4 kB
  • After compression 8.1 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 11.9 kB, which is 26% 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 37.2 kB or 82% of the original size.

Image Optimization

-26%

Potential reduce by 2.8 MB

  • Original 10.7 MB
  • After minification 7.9 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. Obviously, Ixtapa Palace Resort needs image optimization as it can save up to 2.8 MB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-31%

Potential reduce by 247.2 kB

  • Original 802.9 kB
  • After minification 794.8 kB
  • After compression 555.7 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 247.2 kB or 31% of the original size.

CSS Optimization

-72%

Potential reduce by 261.1 kB

  • Original 365.0 kB
  • After minification 343.1 kB
  • After compression 103.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. Ixtapapalaceresort.com needs all CSS files to be minified and compressed as it can save up to 261.1 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (44%)

Requests Now

86

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ixtapa Palace Resort. 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 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ixtapapalaceresort.com

ixtapapalaceresort.com

114 ms

www.ixtapapalaceresort.com

www.ixtapapalaceresort.com

112 ms

www.ixtapapalaceresort.com

www.ixtapapalaceresort.com

253 ms

css

css

40 ms

bootstrap.min.css

bootstrap.min.css

207 ms

font-awesome.min.css

font-awesome.min.css

217 ms

owl.carousel.css

owl.carousel.css

158 ms

owl.theme.css

owl.theme.css

159 ms

owl.transitions.css

owl.transitions.css

159 ms

cs-select.css

cs-select.css

218 ms

bootstrap-datepicker3.min.css

bootstrap-datepicker3.min.css

263 ms

freepik.hotels.css

freepik.hotels.css

219 ms

style.css

style.css

308 ms

jquery.min.js

jquery.min.js

363 ms

modernizr.custom.min.js

modernizr.custom.min.js

260 ms

api.js

api.js

45 ms

js

js

95 ms

bootstrap.min.js

bootstrap.min.js

403 ms

owl.carousel.min.js

owl.carousel.min.js

405 ms

jssor.slider.mini.js

jssor.slider.mini.js

405 ms

classie.js

classie.js

357 ms

selectFx.js

selectFx.js

486 ms

bootstrap-datepicker.min.js

bootstrap-datepicker.min.js

487 ms

starrr.min.js

starrr.min.js

486 ms

nivo-lightbox.min.js

nivo-lightbox.min.js

486 ms

jquery.shuffle.min.js

jquery.shuffle.min.js

487 ms

js

js

51 ms

gmaps.min.js

gmaps.min.js

545 ms

jquery.parallax-1.1.3.js

jquery.parallax-1.1.3.js

544 ms

script.js

script.js

544 ms

recaptcha__en.js

recaptcha__en.js

197 ms

fbevents.js

fbevents.js

105 ms

t_eYkL_7E30

t_eYkL_7E30

387 ms

logo.png

logo.png

160 ms

slide-0-1920x900.jpg

slide-0-1920x900.jpg

920 ms

stars.png

stars.png

159 ms

slide-1-1920x900.jpg

slide-1-1920x900.jpg

422 ms

slide-2-1920x900.jpg

slide-2-1920x900.jpg

921 ms

slide-3-1920x900.jpg

slide-3-1920x900.jpg

1206 ms

slide-4-1920x900.jpg

slide-4-1920x900.jpg

1210 ms

cur-arrow-left.png

cur-arrow-left.png

491 ms

cur-arrow-right.png

cur-arrow-right.png

916 ms

rooms-hotel-4.jpg

rooms-hotel-4.jpg

919 ms

rooms-senior-4.jpg

rooms-senior-4.jpg

1273 ms

rooms-senior-6.jpg

rooms-senior-6.jpg

1071 ms

about-bg.png

about-bg.png

1070 ms

page-title.png

page-title.png

1397 ms

clients-bg.png

clients-bg.png

1207 ms

blockquote.png

blockquote.png

1205 ms

part-logo-3.png

part-logo-3.png

1273 ms

part-logo-1.png

part-logo-1.png

1274 ms

rooms-junior-5.jpg

rooms-junior-5.jpg

1274 ms

rooms-royal-5.jpg

rooms-royal-5.jpg

1274 ms

rooms-royal-7.jpg

rooms-royal-7.jpg

1542 ms

rooms-royal-1.jpg

rooms-royal-1.jpg

1402 ms

rooms-junior-4.jpg

rooms-junior-4.jpg

1403 ms

rooms-junior-5.jpg

rooms-junior-5.jpg

1404 ms

rooms-royal-5.jpg

rooms-royal-5.jpg

1404 ms

rooms-royal-7.jpg

rooms-royal-7.jpg

1540 ms

rooms-hotel-4.jpg

rooms-hotel-4.jpg

1540 ms

rooms-royal-1.jpg

rooms-royal-1.jpg

1458 ms

rooms-junior-4.jpg

rooms-junior-4.jpg

1457 ms

rooms-senior-4.jpg

rooms-senior-4.jpg

1457 ms

ins-01.png

ins-01.png

1461 ms

ins-02.png

ins-02.png

1459 ms

ins-03.png

ins-03.png

1461 ms

js

js

275 ms

analytics.js

analytics.js

269 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

308 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

368 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

404 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

379 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

404 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf

402 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtY.ttf

402 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtY.ttf

401 ms

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_qiTXtHA_A.ttf

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_qiTXtHA_A.ttf

446 ms

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_k-UXtHA_A.ttf

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_k-UXtHA_A.ttf

447 ms

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_gGUXtHA_A.ttf

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_gGUXtHA_A.ttf

447 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1405 ms

hotels.ttf

hotels.ttf

1401 ms

ins-05.png

ins-05.png

1393 ms

ins-04.png

ins-04.png

1391 ms

ins-06.png

ins-06.png

1391 ms

widget.min.js

widget.min.js

896 ms

fallback

fallback

113 ms

www-player.css

www-player.css

61 ms

www-embed-player.js

www-embed-player.js

141 ms

base.js

base.js

236 ms

collect

collect

138 ms

ins-07.png

ins-07.png

1117 ms

fallback__ltr.css

fallback__ltr.css

35 ms

ins-08.png

ins-08.png

1061 ms

css

css

406 ms

collect

collect

515 ms

ad_status.js

ad_status.js

370 ms

ins-09.png

ins-09.png

633 ms

logo_48.png

logo_48.png

151 ms

6mt_jkCC8QEMfVv4UaXe0WVRezbgElH9_VSMBGBwk28.js

6mt_jkCC8QEMfVv4UaXe0WVRezbgElH9_VSMBGBwk28.js

202 ms

embed.js

embed.js

147 ms

ga-audiences

ga-audiences

197 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

36 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

36 ms

id

id

59 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

23 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

23 ms

Accessibility Review

ixtapapalaceresort.com accessibility score

79

Accessibility Issues

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

High

ARIA input fields do not have accessible names

High

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

High

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

ixtapapalaceresort.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

ixtapapalaceresort.com SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

ixtapapalaceresort.com

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