Tools & Wizards About Us
exeltur.com screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

exeltur.com

EXELTUR: Cancun Airport Shuttle - Private Transportation & Taxi Service

Page Load Speed

6 sec in total

First Response

1.3 sec

Resources Loaded

3.1 sec

Page Rendered

1.5 sec

exeltur.com screenshot

About Website

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

Exeltur.com is a Cancun Airport Transportation and Transfer service company. We offer private transfer, taxi or shuttle service to anywhere in Cancun, Puerto Juarez, Playa Mujeres, Puerto Morelos, Pla...

Visit exeltur.com

Key Findings

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

Performance Metrics

exeltur.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value42.8 s

0/100

25%

SI (Speed Index)

Value18.1 s

0/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value28.8 s

0/100

10%

Network Requests Diagram

exeltur.com

1338 ms

main.min.css

42 ms

joinchat-btn.min.css

31 ms

frontend-lite.min.css

47 ms

swiper.min.css

34 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 88% of them (66 requests) were addressed to the original Exeltur.com, 8% (6 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Exeltur.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (26%)

Content Size

8.6 MB

After Optimization

6.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Exeltur.com main page is 8.6 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 6.7 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 156.9 kB

  • Original 187.9 kB
  • After minification 184.1 kB
  • After compression 31.0 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 156.9 kB or 84% of the original size.

Image Optimization

-12%

Potential reduce by 776.6 kB

  • Original 6.7 MB
  • After minification 6.0 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, EXELTUR needs image optimization as it can save up to 776.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 343.5 kB

  • Original 499.9 kB
  • After minification 499.9 kB
  • After compression 156.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 343.5 kB or 69% of the original size.

CSS Optimization

-84%

Potential reduce by 966.8 kB

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

Requests Breakdown

Number of requests can be reduced by 50 (75%)

Requests Now

67

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

exeltur.com

exeltur.com

1338 ms

main.min.css

main.min.css

42 ms

joinchat-btn.min.css

joinchat-btn.min.css

31 ms

frontend-lite.min.css

frontend-lite.min.css

47 ms

swiper.min.css

swiper.min.css

34 ms

post-9.css

post-9.css

29 ms

frontend-lite.min.css

frontend-lite.min.css

33 ms

all.min.css

all.min.css

52 ms

v4-shims.min.css

v4-shims.min.css

40 ms

post-12.css

post-12.css

58 ms

icomoon_brands.css

icomoon_brands.css

55 ms

devicons.min.css

devicons.min.css

60 ms

elegant.css

elegant.css

61 ms

elusive-icons.min.css

elusive-icons.min.css

61 ms

icofont.min.css

icofont.min.css

65 ms

icomoon.css

icomoon.css

62 ms

iconic.css

iconic.css

63 ms

ionicons.min.css

ionicons.min.css

71 ms

linearicons.css

linearicons.css

68 ms

line-awesome.min.css

line-awesome.min.css

73 ms

lineicons.css

lineicons.css

69 ms

materialdesignicons.min.css

materialdesignicons.min.css

80 ms

open-iconic.css

open-iconic.css

72 ms

simple-line-icons.css

simple-line-icons.css

77 ms

themify.css

themify.css

78 ms

css

css

38 ms

jquery.min.js

jquery.min.js

106 ms

v4-shims.min.js

v4-shims.min.js

105 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

19 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

23 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

27 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

29 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

30 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

30 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

11 ms

logo.png

logo.png

19 ms

Diseno-sin-titulo.jpg

Diseno-sin-titulo.jpg

19 ms

TAXI-DRIVER-CANCUN-MEXICO-23.jpg

TAXI-DRIVER-CANCUN-MEXICO-23.jpg

18 ms

TAXI-DRIVER-CANCUN-MEXICO-22.jpg

TAXI-DRIVER-CANCUN-MEXICO-22.jpg

12 ms

TAXI-DRIVER-CANCUN-MEXICO-21.jpg

TAXI-DRIVER-CANCUN-MEXICO-21.jpg

13 ms

TAXI-DRIVER-CANCUN-MEXICO-20.jpg

TAXI-DRIVER-CANCUN-MEXICO-20.jpg

21 ms

TAXI-DRIVER-CANCUN-MEXICO-19.jpg

TAXI-DRIVER-CANCUN-MEXICO-19.jpg

22 ms

TAXI-DRIVER-CANCUN-MEXICO-18.jpg

TAXI-DRIVER-CANCUN-MEXICO-18.jpg

23 ms

TAXI-DRIVER-CANCUN-MEXICO-17.jpg

TAXI-DRIVER-CANCUN-MEXICO-17.jpg

74 ms

TAXI-DRIVER-CANCUN-MEXICO-16.jpg

TAXI-DRIVER-CANCUN-MEXICO-16.jpg

73 ms

TAXI-DRIVER-CANCUN-MEXICO-15.jpg

TAXI-DRIVER-CANCUN-MEXICO-15.jpg

29 ms

widget-icon-box.min.css

widget-icon-box.min.css

30 ms

flatpickr.min.css

flatpickr.min.css

29 ms

animations.min.css

animations.min.css

29 ms

frontend.min.js

frontend.min.js

71 ms

joinchat.min.js

joinchat.min.js

72 ms

jquery-migrate.min.js

jquery-migrate.min.js

72 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

72 ms

flatpickr.min.js

flatpickr.min.js

73 ms

jquery-numerator.min.js

jquery-numerator.min.js

73 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

74 ms

webpack.runtime.min.js

webpack.runtime.min.js

73 ms

frontend-modules.min.js

frontend-modules.min.js

74 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

74 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

74 ms

wp-polyfill.min.js

wp-polyfill.min.js

74 ms

hooks.min.js

hooks.min.js

75 ms

i18n.min.js

i18n.min.js

74 ms

frontend.min.js

frontend.min.js

75 ms

waypoints.min.js

waypoints.min.js

75 ms

core.min.js

core.min.js

77 ms

frontend.min.js

frontend.min.js

74 ms

elements-handlers.min.js

elements-handlers.min.js

75 ms

jquery.sticky.min.js

jquery.sticky.min.js

75 ms

bg2.png

bg2.png

66 ms

tulum-taxi-driver-viaje-seguro.jpg

tulum-taxi-driver-viaje-seguro.jpg

58 ms

bg33.png

bg33.png

80 ms

embed

embed

369 ms

materialdesignicons-webfont.woff

materialdesignicons-webfont.woff

38 ms

js

js

50 ms

Accessibility Review

exeltur.com accessibility score

94

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.

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

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

exeltur.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

exeltur.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    ES

  • Encoding

    UTF-8

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

exeltur.com

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