Tools & Wizards About Us
planetamex.com screenshot

Report Summary

  • 75

    Performance

    Renders faster than
    83% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 42

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

planetamex.com

First Class & Business Class Discounts, Planetamex.

Page Load Speed

1.7 sec in total

First Response

145 ms

Resources Loaded

1.4 sec

Page Rendered

99 ms

planetamex.com screenshot

About Website

Visit planetamex.com now to see the best up-to-date Planetamex content and also check out these interesting facts you probably never knew about planetamex.com

Exclusive discounts on First and Business Class International airfare. Planetamex. specializes solely in lower-priced premium tickets for overseas travel on all major airlines

Visit planetamex.com

Key Findings

We analyzed Planetamex.com page load time and found that the first response time was 145 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

planetamex.com performance score

75

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

50/100

25%

SI (Speed Index)

Value3.6 s

86/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.046

99/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

planetamex.com

145 ms

www.planetamex.com

212 ms

styles.css

213 ms

hf_styles.css

214 ms

jquery-1.10.1.min.js

18 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 24% of them (6 requests) were addressed to the original Planetamex.com, 24% (6 requests) were made to Content.onlineagency.com and 8% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (881 ms) relates to the external source Blogclarity.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 48.2 kB (38%)

Content Size

126.0 kB

After Optimization

77.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Planetamex.com main page is 126.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Javascripts take 95.9 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 15.9 kB

  • Original 21.2 kB
  • After minification 19.2 kB
  • After compression 5.3 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 15.9 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 62 B

  • Original 7.7 kB
  • After minification 7.7 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. Planetamex images are well optimized though.

JavaScript Optimization

-33%

Potential reduce by 32.1 kB

  • Original 95.9 kB
  • After minification 95.9 kB
  • After compression 63.8 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 32.1 kB or 33% of the original size.

CSS Optimization

-13%

Potential reduce by 159 B

  • Original 1.2 kB
  • After minification 1.2 kB
  • After compression 1.1 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. Planetamex.com needs all CSS files to be minified and compressed as it can save up to 159 B or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (32%)

Requests Now

22

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

planetamex.com

planetamex.com

145 ms

www.planetamex.com

www.planetamex.com

212 ms

styles.css

styles.css

213 ms

hf_styles.css

hf_styles.css

214 ms

jquery-1.10.1.min.js

jquery-1.10.1.min.js

18 ms

conversion.js

conversion.js

42 ms

counter.js

counter.js

44 ms

counter.js

counter.js

41 ms

hf_script.js

hf_script.js

233 ms

blogclarity.com

blogclarity.com

881 ms

ga.js

ga.js

20 ms

arrow-big.jpg

arrow-big.jpg

52 ms

65 ms

wf_arrow-small.jpg

wf_arrow-small.jpg

81 ms

cooktravelheader2.jpg

cooktravelheader2.jpg

80 ms

wf_clickforquote.gif

wf_clickforquote.gif

43 ms

__utm.gif

__utm.gif

15 ms

25 ms

wf_copyback.jpg

wf_copyback.jpg

45 ms

ad_right2.jpg

ad_right2.jpg

77 ms

t.php

t.php

131 ms

analytics.js

analytics.js

17 ms

logger.aspx

logger.aspx

39 ms

collect

collect

12 ms

js

js

69 ms

Accessibility Review

planetamex.com accessibility score

86

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

planetamex.com best practices score

42

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

planetamex.com SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

planetamex.com

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