Tools & Wizards About Us

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

gtbe.mx

GT Belenes | La mejor opción de entretenimiento y restaurantes

Page Load Speed

5.3 sec in total

First Response

236 ms

Resources Loaded

4.8 sec

Page Rendered

258 ms

About Website

Visit gtbe.mx now to see the best up-to-date GT Be content and also check out these interesting facts you probably never knew about gtbe.mx

Somos más que un centro comercial, aquí encontrarás las mejores opciones de entretenimiento y restaurantes.

Visit gtbe.mx

Key Findings

We analyzed Gtbe.mx page load time and found that the first response time was 236 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

gtbe.mx performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

46/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value2,200 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.064

97/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

gtbe.mx

236 ms

granterrazabelenes.com.mx

99 ms

granterrazabelenes.com.mx

268 ms

sbi-styles.min.css

34 ms

style.min.css

23 ms

Our browser made a total of 137 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Gtbe.mx, 98% (134 requests) were made to Granterrazabelenes.com.mx and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Granterrazabelenes.com.mx.

Page Optimization Overview & Recommendations

Page size can be reduced by 377.0 kB (3%)

Content Size

11.1 MB

After Optimization

10.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gtbe.mx main page is 11.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 10.5 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 287.9 kB

  • Original 346.0 kB
  • After minification 345.9 kB
  • After compression 58.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. 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 287.9 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 88.4 kB

  • Original 10.5 MB
  • After minification 10.4 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. GT Be images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 480 B

  • Original 82.9 kB
  • After minification 82.9 kB
  • After compression 82.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 239 B

  • Original 201.7 kB
  • After minification 201.7 kB
  • After compression 201.4 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. Gtbe.mx has all CSS files already compressed.

Requests Breakdown

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

Requests Now

125

After Optimization

85

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

gtbe.mx accessibility score

70

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-*] attributes do not match their roles

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

gtbe.mx 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

SEO Factors

gtbe.mx SEO score

84

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

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 Gtbe.mx 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 Gtbe.mx 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

Open Graph data is detected on the main page of GT Be. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: