Tools & Wizards About Us
futebolcard.com.br screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

futebolcard.com.br

FutebolCard | O Maior Portal de Venda de Ingresso de Futebol do Brasil

Page Load Speed

7.8 sec in total

First Response

125 ms

Resources Loaded

3.6 sec

Page Rendered

4.1 sec

futebolcard.com.br screenshot

About Website

Click here to check amazing Futebol Card content. Otherwise, check out these important facts you probably never knew about futebolcard.com.br

Conte com a FutebolCard para comprar ingressos do seu time favorito com segurança e agilidade. Drible as filas!"

Visit futebolcard.com.br

Key Findings

We analyzed Futebolcard.com.br page load time and found that the first response time was 125 ms and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

futebolcard.com.br performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value27.2 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value2,770 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value26.9 s

0/100

10%

Network Requests Diagram

futebolcard.com.br

125 ms

www.futebolcard.com

1222 ms

bootstrap-icons.css

32 ms

toastr.min.css

24 ms

lightbox.min.css

528 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Futebolcard.com.br, 53% (51 requests) were made to S3-sa-east-1.amazonaws.com and 34% (33 requests) were made to Futebolcard.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source S3-sa-east-1.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (25%)

Content Size

5.9 MB

After Optimization

4.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Futebolcard.com.br main page is 5.9 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. Images take 4.3 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 62.5 kB

  • Original 72.1 kB
  • After minification 63.0 kB
  • After compression 9.6 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 9.1 kB, which is 13% 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 62.5 kB or 87% of the original size.

Image Optimization

-8%

Potential reduce by 351.9 kB

  • Original 4.3 MB
  • After minification 4.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. Futebol Card images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 1.0 MB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 377.2 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 1.0 MB or 73% of the original size.

CSS Optimization

-19%

Potential reduce by 25.6 kB

  • Original 134.9 kB
  • After minification 134.9 kB
  • After compression 109.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. Futebolcard.com.br needs all CSS files to be minified and compressed as it can save up to 25.6 kB or 19% of the original size.

Requests Breakdown

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

Requests Now

89

After Optimization

57

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

futebolcard.com.br

futebolcard.com.br

125 ms

www.futebolcard.com

www.futebolcard.com

1222 ms

bootstrap-icons.css

bootstrap-icons.css

32 ms

toastr.min.css

toastr.min.css

24 ms

lightbox.min.css

lightbox.min.css

528 ms

image-zoom.css

image-zoom.css

40 ms

fcard-maps.css

fcard-maps.css

50 ms

faq.css

faq.css

62 ms

aos.css

aos.css

51 ms

icofont.min.css

icofont.min.css

53 ms

hover-min.css

hover-min.css

64 ms

croppie.css

croppie.css

70 ms

font-awesome.min.css

font-awesome.min.css

74 ms

classic.date.css

classic.date.css

72 ms

classic.css

classic.css

71 ms

bootstrap.min.css

bootstrap.min.css

837 ms

swiper.min.css

swiper.min.css

84 ms

sass.css

sass.css

579 ms

main.css

main.css

679 ms

dd.css

dd.css

91 ms

skin2.css

skin2.css

130 ms

flags.css

flags.css

109 ms

Stake-BANNER-(1368X250)_v2.png

Stake-BANNER-(1368X250)_v2.png

1132 ms

home.png

home.png

122 ms

tickets.png

tickets.png

153 ms

cart.png

cart.png

153 ms

perfil.png

perfil.png

173 ms

logo-futebolcard.svg

logo-futebolcard.svg

683 ms

disponivel-appstore.png

disponivel-appstore.png

193 ms

disponivel-playstore.png

disponivel-playstore.png

210 ms

mobile1.png

mobile1.png

227 ms

mobile2.png

mobile2.png

251 ms

FFCS_Legends(1368x250)_v2.png

FFCS_Legends(1368x250)_v2.png

900 ms

INGRESSO-PROTEGIDO-BANNER-(1368x250)_v2.png

INGRESSO-PROTEGIDO-BANNER-(1368x250)_v2.png

1125 ms

FCSHOP-BANNER-(1368x250)_v2.png

FCSHOP-BANNER-(1368x250)_v2.png

992 ms

banner-cashback-stake.jpg

banner-cashback-stake.jpg

747 ms

FC%20formato.png

FC%20formato.png

992 ms

1%20(1).png

1%20(1).png

1129 ms

banner-fc-ingresso-protegido.png

banner-fc-ingresso-protegido.png

1128 ms

659ebbc1684d5.png

659ebbc1684d5.png

1126 ms

660b01bfb9fca.png

660b01bfb9fca.png

1126 ms

65b11587b2fb1.png

65b11587b2fb1.png

1207 ms

659ef70136c16.png

659ef70136c16.png

1204 ms

659ef5baf03e4.png

659ef5baf03e4.png

1223 ms

659d437467221.png

659d437467221.png

1228 ms

659ed44698330.png

659ed44698330.png

1235 ms

65eb98682500c.png

65eb98682500c.png

1242 ms

659d4206e3c9e.png

659d4206e3c9e.png

1334 ms

659ecd52ea483.png

659ecd52ea483.png

1332 ms

659d45efdbd41.png

659d45efdbd41.png

1352 ms

659ed9a02b38e.png

659ed9a02b38e.png

1356 ms

659ee964053dd.png

659ee964053dd.png

1361 ms

659ecf049c926.png

659ecf049c926.png

1379 ms

659d43ea31086.png

659d43ea31086.png

1456 ms

6602ffcd70276.png

6602ffcd70276.png

1458 ms

660d6ed781af4.png

660d6ed781af4.png

1480 ms

659d47e17f698.png

659d47e17f698.png

1484 ms

660d6dbabce93.png

660d6dbabce93.png

1488 ms

659d46ef69dba.png

659d46ef69dba.png

1504 ms

65e9dda5ca503.png

65e9dda5ca503.png

1586 ms

659ef23b5792f.png

659ef23b5792f.png

1582 ms

659ea400adfc6.png

659ea400adfc6.png

1604 ms

659ef5f97da1a.png

659ef5f97da1a.png

1613 ms

659ed44f8989b.png

659ed44f8989b.png

1622 ms

659ed9b383210.png

659ed9b383210.png

1633 ms

659ebb222a275.png

659ebb222a275.png

1708 ms

65a0209716643.png

65a0209716643.png

1715 ms

main.cf92e33e.css

main.cf92e33e.css

485 ms

main.js

main.js

1056 ms

rocket-loader.min.js

rocket-loader.min.js

245 ms

css2

css2

33 ms

65c8d69c57ea6.png

65c8d69c57ea6.png

998 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

32 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

67 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

68 ms

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

1 ms

bootstrap-icons.woff

bootstrap-icons.woff

31 ms

659e9dbfbd2b6.png

659e9dbfbd2b6.png

854 ms

65a024a182b55.png

65a024a182b55.png

766 ms

659ea5fbab6de.png

659ea5fbab6de.png

770 ms

659ea23af3bda.png

659ea23af3bda.png

713 ms

659ef54d09cf0.png

659ef54d09cf0.png

724 ms

659ecc3e35eeb.png

659ecc3e35eeb.png

743 ms

66211dc39d542.png

66211dc39d542.png

760 ms

659ed86c2c686.png

659ed86c2c686.png

760 ms

659d45135b069.png

659d45135b069.png

773 ms

1711571369bm9tZUFycXVpdm9MaXN0YWdlbQ==FOTO-NO-MUSEU.png

1711571369bm9tZUFycXVpdm9MaXN0YWdlbQ==FOTO-NO-MUSEU.png

784 ms

1714404974bm9tZUFycXVpdm9MaXN0YWdlbQ==banner%20museu.png

1714404974bm9tZUFycXVpdm9MaXN0YWdlbQ==banner%20museu.png

781 ms

1713292209bm9tZUFycXVpdm9MaXN0YWdlbQ==Arrai%C3%A1%20do%20Seu%20Timbu%20-%20510x255.png

1713292209bm9tZUFycXVpdm9MaXN0YWdlbQ==Arrai%C3%A1%20do%20Seu%20Timbu%20-%20510x255.png

782 ms

1710944601bm9tZUFycXVpdm9MaXN0YWdlbQ==JOTA%20v1%20(2).jpg

1710944601bm9tZUFycXVpdm9MaXN0YWdlbQ==JOTA%20v1%20(2).jpg

789 ms

1710944650bm9tZUFycXVpdm9MaXN0YWdlbQ==IRONMAIDEN%20v1%20(1).jpg

1710944650bm9tZUFycXVpdm9MaXN0YWdlbQ==IRONMAIDEN%20v1%20(1).jpg

782 ms

fbevents.js

fbevents.js

74 ms

gtm.js

gtm.js

123 ms

jquery.min.js

jquery.min.js

21 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

44 ms

popper.min.js

popper.min.js

50 ms

Accessibility Review

futebolcard.com.br accessibility score

76

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

futebolcard.com.br best practices score

67

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

Missing source maps for large first-party JavaScript

SEO Factors

futebolcard.com.br SEO score

73

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

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Futebolcard.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 Futebolcard.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.

Social Sharing Optimization

futebolcard.com.br

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