6.2 sec in total
340 ms
5.5 sec
283 ms
Click here to check amazing Ticket content for Brazil. Otherwise, check out these important facts you probably never knew about ticket.com.br
Vale refeição, vale alimentação e muitos outros benefícios para empresas, funcionários e estabelecimentos!
Visit ticket.com.brWe analyzed Ticket.com.br page load time and found that the first response time was 340 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ticket.com.br performance score
name
value
score
weighting
Value11.0 s
0/100
10%
Value16.5 s
0/100
25%
Value16.5 s
0/100
10%
Value6,690 ms
0/100
30%
Value0.068
96/100
15%
Value31.1 s
0/100
10%
340 ms
253 ms
144 ms
252 ms
275 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 73% of them (96 requests) were addressed to the original Ticket.com.br, 13% (17 requests) were made to Cdn.jsdelivr.net and 7% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Ticket.com.br.
Page size can be reduced by 731.5 kB (68%)
1.1 MB
351.4 kB
In fact, the total size of Ticket.com.br main page is 1.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. 70% of websites need less resources to load. CSS take 462.1 kB which makes up the majority of the site volume.
Potential reduce by 289.8 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 87.1 kB, which is 27% 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 289.8 kB or 90% of the original size.
Potential reduce by 0 B
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. Ticket images are well optimized though.
Potential reduce by 92.6 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 92.6 kB or 40% of the original size.
Potential reduce by 349.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. Ticket.com.br needs all CSS files to be minified and compressed as it can save up to 349.1 kB or 76% of the original size.
Number of requests can be reduced by 91 (79%)
115
24
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ticket. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 42 to 1 for CSS and as a result speed up the page load time.
ticket.com.br
340 ms
www.ticket.com.br
253 ms
common-lib-factor-brand.js
144 ms
common-lib-factor-brand.js
252 ms
common-lib-factor-brand.js
275 ms
jquery-ui.min.css
38 ms
style.min.css
581 ms
pagenavi-css.css
548 ms
swiper.min.css
717 ms
widget-ticket-faq-banner.css
737 ms
widget-ticket-forms-custom.css
274 ms
widget-ticket-modulo-galeria-logos.css
881 ms
widget-box-responsivo.css
816 ms
widget-ticket-calculadora-pat.css
1045 ms
widget-leads-custom.css
1290 ms
default.css
845 ms
main.min.css
1275 ms
theme.css
968 ms
owl.carousel.min.css
37 ms
owl.theme.default.min.css
39 ms
bootstrap.min.css
42 ms
landing-page-conversion.css
1463 ms
porteira.css
1041 ms
jquery.min.js
41 ms
v4-shims.min.js
1542 ms
owl.carousel.min.js
39 ms
OtAutoBlock.js
59 ms
otSDKStub.js
74 ms
slick-carousel-banner.css
1063 ms
slick-carousel-socialmedia.css
1707 ms
slick-carousel-ticketnumbers.css
1637 ms
slick-carousel-products.css
1802 ms
category.css
1953 ms
6bd2ab1de93563ccc2ac555b8f1808de.js
578 ms
dl-menu.css
1629 ms
widget-portal-header-menu.css
2152 ms
widget-title.css
1734 ms
widget-service-button.css
2240 ms
widget-text-media.css
1860 ms
widget-paragraph.css
1899 ms
widget-simple-button.css
1937 ms
widget-leads-lightbox.css
1995 ms
widget-portal-ticket-footer.css
2030 ms
jquery-ui.min.js
39 ms
jquery.validate.min.js
37 ms
jquery.matchHeight-min.js
37 ms
jquery.mask.min.js
38 ms
jquery.maskMoney.min.js
43 ms
jquery.touchSwipe.min.js
39 ms
tagmanager.js
2077 ms
ticket-faq-banner.js
2458 ms
produtos.js
2508 ms
jquery-migrate.min.js
42 ms
slick.min.js
39 ms
parallax.min.js
39 ms
api.js
47 ms
bootstrap.min.js
39 ms
lazysizes.min.js
40 ms
modernizr.custom.js
2168 ms
jquery.dlmenu.js
2579 ms
analytics.js
198 ms
css
210 ms
widget-portal-header-menu.js
2016 ms
slick-carousel-banner.min.js
2046 ms
slick-carousel-socialmedia.min.js
1928 ms
js
34 ms
css2
31 ms
slick-carousel-ticketnumbers.min.js
2337 ms
slick-carousel-products.min.js
1866 ms
category.min.js
2297 ms
widget-portal-ticket-footer.js
1846 ms
ls.unveilhooks.min.js
2206 ms
wp-all.min.js
2223 ms
webpack-pro.runtime.min.js
1837 ms
webpack.runtime.min.js
1891 ms
frontend-modules.min.js
1829 ms
wp-polyfill-inert.min.js
1949 ms
regenerator-runtime.min.js
1943 ms
wp-polyfill.min.js
1727 ms
hooks.min.js
2386 ms
i18n.min.js
1670 ms
eb1608a1-d79a-45b4-b0a3-294f57c7ec15.json
76 ms
post-14349.css
1648 ms
location
64 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff
25 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff
36 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff
46 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff
59 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff
60 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff
60 ms
frontend.min.js
1791 ms
4iCs6KVjbNBYlgo6ew.woff
62 ms
4iCv6KVjbNBYlgoCjC3TtA.woff
61 ms
4iCv6KVjbNBYlgoCxCvTtA.woff
60 ms
waypoints.min.js
1517 ms
core.min.js
1484 ms
frontend.min.js
1685 ms
elements-handlers.min.js
1618 ms
lazyload.min.js
1559 ms
Edenred-Regular.woff
1520 ms
EdenredMedium-Regular.woff
1511 ms
EdenredLight-Regular.woff
1976 ms
EdenredBold-Regular.woff
1567 ms
EdenredBlack-Regular.woff
1867 ms
icomoon.woff
1485 ms
elementor-icons.min.css
172 ms
frontend.min.css
149 ms
post-5803.css
139 ms
all.min.css
155 ms
v4-shims.min.css
265 ms
global.css
1096 ms
post-14789.css
324 ms
Logo-ticket-edenred-header.svg
168 ms
btn-closed.svg
193 ms
btn-search.svg
194 ms
btn-search-desk.svg
900 ms
btn-login.svg
267 ms
btn-login-desk.svg
328 ms
btn-opened.svg
265 ms
btn-compre-online.svg
426 ms
arrow-right.svg
267 ms
arrow-right-active.svg
324 ms
imagem_login-01.png
427 ms
imagem-login-02.png
897 ms
imagem-login-03.png
500 ms
Login.svg
548 ms
Banner-1-usuarios-ticket-app.png
1124 ms
icon-60x60-saldo.svg
600 ms
icon-60x60-senha.svg
700 ms
icon-60x60-desbloquear-cartao.svg
602 ms
icon-60x60-2-via.svg
1124 ms
icon-60x60-app.svg
847 ms
ticket.com.br accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
ticket.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
ticket.com.br 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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ticket.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Ticket.com.br 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.
ticket.com.br
Open Graph data is detected on the main page of Ticket. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: