5.3 sec in total
236 ms
4.8 sec
258 ms
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.mxWe 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.
gtbe.mx performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value4.1 s
46/100
25%
Value5.2 s
60/100
10%
Value2,200 ms
6/100
30%
Value0.064
97/100
15%
Value9.5 s
30/100
10%
236 ms
99 ms
268 ms
34 ms
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 size can be reduced by 377.0 kB (3%)
11.1 MB
10.7 MB
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.
Potential reduce by 287.9 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.
Potential reduce by 88.4 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. GT Be images are well optimized though.
Potential reduce by 480 B
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.
Potential reduce by 239 B
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.
Number of requests can be reduced by 40 (32%)
125
85
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.
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
styles.css
47 ms
team-grid.css
44 ms
fontawesome-team-grid.css
41 ms
animate.css
47 ms
nanoscroller.css
54 ms
uaf.css
77 ms
captcha.min.css
62 ms
style.css
83 ms
style.css
66 ms
grid.min.css
59 ms
js_composer.min.css
101 ms
frontend.css
74 ms
smartslider.min.css
99 ms
jquery.min.js
120 ms
jquery-migrate.min.js
127 ms
effect.min.js
226 ms
effect-slide.min.js
242 ms
css
31 ms
email-decode.min.js
73 ms
v4-shims.min.css
192 ms
all.min.css
259 ms
aos.css
178 ms
ionicons.min.css
262 ms
fontawesome.min.css
333 ms
rs6.css
347 ms
regenerator-runtime.min.js
335 ms
wp-polyfill.min.js
402 ms
woocommerce-hack.js
335 ms
imagesloaded.min.js
340 ms
masonry.min.js
481 ms
jquery.masonry.min.js
491 ms
underscore.min.js
498 ms
aos.js
474 ms
jquery.mega-menu.min.js
487 ms
navigation.js
515 ms
skip-link-focus-fix.js
628 ms
owl.carousel.min.js
619 ms
main.js
654 ms
lazyload.min.js
658 ms
vcd15cbe7772f49c399c6a5babf22c1241717689176015
108 ms
dummy.png
560 ms
13-mas-que-un-centro-belenes.jpg
695 ms
01-mas-que-un-centro-belenes.jpg
846 ms
02-mas-que-un-centro-belenes.jpg
864 ms
03-mas-que-un-centro-belenes.jpg
895 ms
04-mas-que-un-centro-belenes.jpg
793 ms
05-mas-que-un-centro-belenes.jpg
833 ms
06-mas-que-un-centro-belenes.jpg
986 ms
07-mas-que-un-centro-belenes.jpg
1096 ms
08-mas-que-un-centro-belenes.jpg
1179 ms
09-mas-que-un-centro-belenes.jpg
1181 ms
10-mas-que-un-centro-belenes.jpg
1158 ms
11-mas-que-un-centro-belenes.jpg
1194 ms
12-mas-que-un-centro-belenes.jpg
1324 ms
13-mas-que-un-centro-belenes.jpg
1164 ms
01-mas-que-un-centro-belenes.jpg
1222 ms
02-mas-que-un-centro-belenes.jpg
1255 ms
03-mas-que-un-centro-belenes.jpg
1264 ms
04-mas-que-un-centro-belenes.jpg
1177 ms
4447AllRoundGothic-Bold.woff
1278 ms
5873AllRoundGothic-Book.woff
1412 ms
05-mas-que-un-centro-belenes.jpg
1238 ms
06-mas-que-un-centro-belenes.jpg
1241 ms
07-mas-que-un-centro-belenes.jpg
1258 ms
08-mas-que-un-centro-belenes.jpg
1198 ms
fa-solid-900.woff
1400 ms
fa-solid-900.woff
1356 ms
fa-regular-400.woff
1285 ms
fa-regular-400.woff
1223 ms
fa-brands-400.woff
1366 ms
fa-brands-400.woff
1453 ms
ionicons.ttf
1494 ms
09-mas-que-un-centro-belenes.jpg
1278 ms
10-mas-que-un-centro-belenes.jpg
1310 ms
11-mas-que-un-centro-belenes.jpg
1328 ms
12-mas-que-un-centro-belenes.jpg
1368 ms
scroll-top.svg
1364 ms
logo-flower.png
1281 ms
logo-gtb.png
1195 ms
animation.gif
1196 ms
10-belenes-entretenimiento-.jpg
1341 ms
8-belenes-entretenimiento-.jpg
1375 ms
15-belenes-entretenimiento-.jpg
1310 ms
1-belenes-entretenimiento-.jpg
1335 ms
18-belenes-entretenimiento-.jpg
1273 ms
16-belenes-entretenimiento-.jpg
1162 ms
13-belenes-entretenimiento-.jpg
1298 ms
5-belenes-entretenimiento-.jpg
1320 ms
4-belenes-entretenimiento-.jpg
1346 ms
9-belenes-entretenimiento-.jpg
1404 ms
12-belenes-entretenimiento-.jpg
1412 ms
22-belenes-entretenimiento-.jpg
1354 ms
11-belenes-entretenimiento-.jpg
1421 ms
23-belenes-entretenimiento-.jpg
1449 ms
25-belenes-entretenimiento-.jpg
1473 ms
24-belenes-entretenimiento-.jpg
1472 ms
3-belenes-entretenimiento-.jpg
1387 ms
20-belenes-entretenimiento-.jpg
1533 ms
21-belenes-entretenimiento-.jpg
1593 ms
17-belenes-entretenimiento-.jpg
1629 ms
2-belenes-entretenimiento-.jpg
1490 ms
14-belenes-entretenimiento-.jpg
1365 ms
19-belenes-entretenimiento-.jpg
1542 ms
7-belenes-entretenimiento-.jpg
1623 ms
6-belenes-entretenimiento-.jpg
1592 ms
logo-soriana.png
1371 ms
logo-cinepolis.png
1527 ms
logos-office-depot.png
1425 ms
logo-radio-shack.png
1330 ms
subway-1.png
1482 ms
todomoda-1.png
1494 ms
nike-1.png
1465 ms
carl%C2%B4s-Jr.-1.png
1542 ms
icn-wifi.png
1513 ms
icn-security-cam.png
1411 ms
icn-different-capacities.png
1387 ms
icn-parking-lot.png
1347 ms
icn-baby.png
1348 ms
placeholder.png
1353 ms
logo-ltde.svg
1155 ms
logo-ltdc.svg
1309 ms
logo-gtlv.svg
1263 ms
logo-gto.svg
1141 ms
logo-gtc.svg
1178 ms
logo-serviplaza.svg
1180 ms
logo-miyana.svg
1118 ms
logo-palmas-uno.svg
1099 ms
logo-GTB-white.svg
1066 ms
icono-waze-y-maps-01.svg
1026 ms
icono-waze-y-maps-02.svg
1047 ms
logo-ggi-white.svg
1029 ms
chatbot.gif
1280 ms
gtbe.mx accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
gtbe.mx best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
gtbe.mx SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
ES
ES
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.
gtbe.mx
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: