Tools & Wizards About Us
city.fantoken.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

city.fantoken.com

Manchester City Fan Tokens ($CITY) - Fan Token

Page Load Speed

10.5 sec in total

First Response

403 ms

Resources Loaded

9.1 sec

Page Rendered

1 sec

city.fantoken.com screenshot

About Website

Welcome to city.fantoken.com homepage info - get ready to check City Fan Token best content for Turkey right away, or after learning these important things about city.fantoken.com

Visit city.fantoken.com

Key Findings

We analyzed City.fantoken.com page load time and found that the first response time was 403 ms and then it took 10.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

city.fantoken.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value27.9 s

0/100

10%

TBT (Total Blocking Time)

Value3,200 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.038

100/100

15%

TTI (Time to Interactive)

Value32.7 s

0/100

10%

Network Requests Diagram

city.fantoken.com

403 ms

2034 ms

style.min.css

27 ms

style.min.css

47 ms

style.css

51 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original City.fantoken.com, 77% (64 requests) were made to Fantoken.com and 7% (6 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Fantoken.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 234.8 kB (4%)

Content Size

5.3 MB

After Optimization

5.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of City.fantoken.com main page is 5.3 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. 80% 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 5.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 99.6 kB

  • Original 121.3 kB
  • After minification 116.3 kB
  • After compression 21.7 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 99.6 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 132.6 kB

  • Original 5.0 MB
  • After minification 4.8 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. City Fan Token images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 228 B

  • Original 159.0 kB
  • After minification 159.0 kB
  • After compression 158.7 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

-3%

Potential reduce by 2.4 kB

  • Original 76.4 kB
  • After minification 76.4 kB
  • After compression 74.0 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. City.fantoken.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 54 (73%)

Requests Now

74

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

city.fantoken.com

city.fantoken.com

403 ms

2034 ms

style.min.css

style.min.css

27 ms

style.min.css

style.min.css

47 ms

style.css

style.css

51 ms

elementor-icons.min.css

elementor-icons.min.css

66 ms

custom-frontend-lite.min.css

custom-frontend-lite.min.css

57 ms

swiper.min.css

swiper.min.css

64 ms

post-7.css

post-7.css

47 ms

custom-pro-frontend-lite.min.css

custom-pro-frontend-lite.min.css

66 ms

post-10620.css

post-10620.css

73 ms

post-11992.css

post-11992.css

74 ms

css

css

49 ms

fontawesome.min.css

fontawesome.min.css

98 ms

brands.min.css

brands.min.css

76 ms

solid.min.css

solid.min.css

81 ms

language-cookie.js

language-cookie.js

76 ms

script.min.js

script.min.js

107 ms

js

js

89 ms

custom-pro-widget-flip-box.min.css

custom-pro-widget-flip-box.min.css

92 ms

custom-widget-icon-list.min.css

custom-widget-icon-list.min.css

93 ms

custom-pro-widget-call-to-action.min.css

custom-pro-widget-call-to-action.min.css

89 ms

widget-animated-headline.min.css

widget-animated-headline.min.css

196 ms

custom-pro-widget-nav-menu.min.css

custom-pro-widget-nav-menu.min.css

193 ms

animations.min.css

animations.min.css

193 ms

navigation.js

navigation.js

251 ms

jquery.min.js

jquery.min.js

206 ms

jquery-migrate.min.js

jquery-migrate.min.js

251 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

250 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

249 ms

webpack.runtime.min.js

webpack.runtime.min.js

249 ms

frontend-modules.min.js

frontend-modules.min.js

250 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

252 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

437 ms

wp-polyfill.min.js

wp-polyfill.min.js

251 ms

hooks.min.js

hooks.min.js

313 ms

i18n.min.js

i18n.min.js

251 ms

frontend.min.js

frontend.min.js

252 ms

waypoints.min.js

waypoints.min.js

312 ms

core.min.js

core.min.js

297 ms

frontend.min.js

frontend.min.js

281 ms

elements-handlers.min.js

elements-handlers.min.js

281 ms

fbevents.js

fbevents.js

149 ms

gtm.js

gtm.js

148 ms

CITYWEBBG-2.jpg

CITYWEBBG-2.jpg

1116 ms

Google_Play_Button-1.png

Google_Play_Button-1.png

248 ms

App_Store_Button-1.png

App_Store_Button-1.png

248 ms

city_token-2.svg

city_token-2.svg

561 ms

Man-City-player-image.webp

Man-City-player-image.webp

819 ms

QR_CITY-2.svg

QR_CITY-2.svg

563 ms

Locker_Room-3.jpg

Locker_Room-3.jpg

248 ms

Locker_Room-2.png

Locker_Room-2.png

247 ms

Screenshot-2021-11-15-at-14.14.03-2.png

Screenshot-2021-11-15-at-14.14.03-2.png

312 ms

Screenshot-2021-11-15-at-13.12.27-2.png

Screenshot-2021-11-15-at-13.12.27-2.png

1154 ms

1920px-Etihad_Stadium-2.jpg

1920px-Etihad_Stadium-2.jpg

351 ms

Meet-your-hero-image-MC-scaled-1.webp

Meet-your-hero-image-MC-scaled-1.webp

424 ms

slphome_contentblock_image2-2.png

slphome_contentblock_image2-2.png

461 ms

Pre-footer_phone-desktop-2-2.png

Pre-footer_phone-desktop-2-2.png

491 ms

Pre-footer_phone-mobile-2-2-2.png

Pre-footer_phone-mobile-2-2-2.png

468 ms

Socios_Logo-lite.svg

Socios_Logo-lite.svg

513 ms

Asset-3.svg

Asset-3.svg

534 ms

pre-footer_background.jpg

pre-footer_background.jpg

534 ms

GalanoBold.woff

GalanoBold.woff

788 ms

GalanoMedium.woff

GalanoMedium.woff

867 ms

fa-solid-900.woff

fa-solid-900.woff

1056 ms

PPMonumentExtended-Medium.woff

PPMonumentExtended-Medium.woff

1119 ms

PPMonumentExtended-Regular.woff

PPMonumentExtended-Regular.woff

1391 ms

PPMonumentExtended-Black.woff

PPMonumentExtended-Black.woff

1407 ms

fa-brands-400.woff

fa-brands-400.woff

1477 ms

js

js

56 ms

js

js

156 ms

js

js

113 ms

destination

destination

188 ms

scevent.min.js

scevent.min.js

145 ms

uwt.js

uwt.js

180 ms

pixie.js

pixie.js

141 ms

events.js

events.js

137 ms

adsct

adsct

136 ms

adsct

adsct

207 ms

adsct

adsct

194 ms

adsct

adsct

201 ms

adsct

adsct

203 ms

adsct

adsct

133 ms

Accessibility Review

city.fantoken.com accessibility score

86

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

Links do not have a discernible name

Best Practices

city.fantoken.com best practices score

83

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

Browser errors were logged to the console

SEO Factors

city.fantoken.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

    EN

  • Encoding

    UTF-8

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

city.fantoken.com

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