Tools & Wizards About Us
fcmiamicity.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

fcmiamicity.com

FC Miami City | The Official USL2 & USLW Team of Miami

Page Load Speed

3.5 sec in total

First Response

344 ms

Resources Loaded

2.5 sec

Page Rendered

701 ms

fcmiamicity.com screenshot

About Website

Click here to check amazing FC Miami City content. Otherwise, check out these important facts you probably never knew about fcmiamicity.com

FC Miami City® is the official USL2 and USLW team of Miami. #Path2Pro #WeAreMiami #SomosMiami

Visit fcmiamicity.com

Key Findings

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

Performance Metrics

fcmiamicity.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value17.8 s

0/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value3,170 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.158

73/100

15%

TTI (Time to Interactive)

Value18.3 s

3/100

10%

Network Requests Diagram

www.fcmiamicity.com

344 ms

gtm.js

73 ms

styles.css

31 ms

settings.css

48 ms

fontello.css

39 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 76% of them (83 requests) were addressed to the original Fcmiamicity.com, 15% (16 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (616 ms) belongs to the original domain Fcmiamicity.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 368.0 kB (10%)

Content Size

3.9 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fcmiamicity.com main page is 3.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. Only a small number of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 343.2 kB

  • Original 382.6 kB
  • After minification 370.7 kB
  • After compression 39.4 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 343.2 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.5 MB
  • After minification 2.5 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. FC Miami City images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 7.2 kB

  • Original 603.1 kB
  • After minification 603.1 kB
  • After compression 595.9 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

-5%

Potential reduce by 17.7 kB

  • Original 384.4 kB
  • After minification 384.2 kB
  • After compression 366.7 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. Fcmiamicity.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 80 (91%)

Requests Now

88

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.fcmiamicity.com

www.fcmiamicity.com

344 ms

gtm.js

gtm.js

73 ms

styles.css

styles.css

31 ms

settings.css

settings.css

48 ms

fontello.css

fontello.css

39 ms

dashicons.min.css

dashicons.min.css

106 ms

sportspress.css

sportspress.css

58 ms

icons.css

icons.css

45 ms

css

css

51 ms

sportspress-style.css

sportspress-style.css

50 ms

sportspress-style-ltr.css

sportspress-style-ltr.css

55 ms

trx_addons_icons.css

trx_addons_icons.css

77 ms

swiper.min.css

swiper.min.css

78 ms

magnific-popup.min.css

magnific-popup.min.css

63 ms

__styles.css

__styles.css

82 ms

trx_addons.animation.css

trx_addons.animation.css

79 ms

style.css

style.css

93 ms

elementor-icons.min.css

elementor-icons.min.css

91 ms

frontend.min.css

frontend.min.css

105 ms

swiper.min.css

swiper.min.css

114 ms

frontend.min.css

frontend.min.css

119 ms

css

css

50 ms

fontello.css

fontello.css

139 ms

style.css

style.css

132 ms

__plugins.css

__plugins.css

113 ms

__custom.css

__custom.css

140 ms

__colors-default.css

__colors-default.css

140 ms

__colors-dark.css

__colors-dark.css

146 ms

__colors-alter.css

__colors-alter.css

153 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

152 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

151 ms

skin.css

skin.css

159 ms

style.css

style.css

161 ms

__responsive.css

__responsive.css

159 ms

__responsive.css

__responsive.css

167 ms

skin-responsive.css

skin-responsive.css

162 ms

css

css

45 ms

jquery.min.js

jquery.min.js

160 ms

jquery-migrate.min.js

jquery-migrate.min.js

162 ms

js

js

85 ms

animations.min.css

animations.min.css

160 ms

api.js

api.js

41 ms

e-202437.js

e-202437.js

24 ms

bootstrap-frontend.css

bootstrap-frontend.css

394 ms

blueimp-gallery.min.css

blueimp-gallery.min.css

378 ms

fag-shortcode-style.css

fag-shortcode-style.css

368 ms

fontawesome.min.css

fontawesome.min.css

365 ms

brands.min.css

brands.min.css

360 ms

hooks.min.js

hooks.min.js

360 ms

i18n.min.js

i18n.min.js

355 ms

index.js

index.js

354 ms

index.js

index.js

345 ms

jquery.dataTables.min.js

jquery.dataTables.min.js

332 ms

sportspress.js

sportspress.js

332 ms

swiper.min.js

swiper.min.js

330 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

321 ms

__scripts.js

__scripts.js

321 ms

anchor.js

anchor.js

310 ms

superfish.min.js

superfish.min.js

300 ms

wp-polyfill.min.js

wp-polyfill.min.js

298 ms

index.js

index.js

297 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

279 ms

__scripts.js

__scripts.js

273 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

275 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

273 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

264 ms

imagesloaded.min.js

imagesloaded.min.js

260 ms

masonry.min.js

masonry.min.js

259 ms

bootstrap.min.js

bootstrap.min.js

260 ms

jquery.blueimp-gallery.min.js

jquery.blueimp-gallery.min.js

254 ms

bootstrap-image-gallery.min.js

bootstrap-image-gallery.min.js

255 ms

forms.js

forms.js

252 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

252 ms

webpack.runtime.min.js

webpack.runtime.min.js

253 ms

frontend-modules.min.js

frontend-modules.min.js

252 ms

frontend.min.js

frontend.min.js

253 ms

waypoints.min.js

waypoints.min.js

250 ms

core.min.js

core.min.js

249 ms

pxiEyp8kv8JHgFVrJJnedw.ttf

pxiEyp8kv8JHgFVrJJnedw.ttf

105 ms

pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf

505 ms

pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf

507 ms

pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf

511 ms

pxiGyp8kv8JHgFVrLPTufntF.ttf

pxiGyp8kv8JHgFVrLPTufntF.ttf

508 ms

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

511 ms

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

511 ms

pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf

511 ms

frontend.min.js

frontend.min.js

100 ms

elements-handlers.min.js

elements-handlers.min.js

424 ms

tweenmax.min.js

tweenmax.min.js

423 ms

Sans-titre-2.jpg

Sans-titre-2.jpg

423 ms

cropped-logo-500.png

cropped-logo-500.png

423 ms

Header-FCMIAMI-HOME-1-1.png

Header-FCMIAMI-HOME-1-1.png

616 ms

01.jpg

01.jpg

616 ms

C41I9251.png

C41I9251.png

616 ms

JTUSjIg69CK48gW7PXoo9Wdhzg.ttf

JTUSjIg69CK48gW7PXoo9Wdhzg.ttf

413 ms

trx_addons_icons.woff

trx_addons_icons.woff

607 ms

fontello.woff

fontello.woff

602 ms

pxiDyp8kv8JHgFVrJJLmr19VGdeL.ttf

pxiDyp8kv8JHgFVrJJLmr19VGdeL.ttf

200 ms

pxiDyp8kv8JHgFVrJJLmy15VGdeL.ttf

pxiDyp8kv8JHgFVrJJLmy15VGdeL.ttf

201 ms

pxiDyp8kv8JHgFVrJJLmg1hVGdeL.ttf

pxiDyp8kv8JHgFVrJJLmg1hVGdeL.ttf

280 ms

pxiGyp8kv8JHgFVrJJLufntF.ttf

pxiGyp8kv8JHgFVrJJLufntF.ttf

201 ms

pxiDyp8kv8JHgFVrJJLm21lVGdeL.ttf

pxiDyp8kv8JHgFVrJJLm21lVGdeL.ttf

201 ms

pxiDyp8kv8JHgFVrJJLmv1pVGdeL.ttf

pxiDyp8kv8JHgFVrJJLmv1pVGdeL.ttf

201 ms

pxiAyp8kv8JHgFVrJJLmE0tMMPc.ttf

pxiAyp8kv8JHgFVrJJLmE0tMMPc.ttf

279 ms

fa-brands-400.woff

fa-brands-400.woff

279 ms

wARDj0u

wARDj0u

30 ms

recaptcha__en.js

recaptcha__en.js

268 ms

iframe_api

iframe_api

264 ms

USL-SL-WWC-Bracket-Challenge-1.png

USL-SL-WWC-Bracket-Challenge-1.png

148 ms

Accessibility Review

fcmiamicity.com accessibility score

84

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

fcmiamicity.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

fcmiamicity.com SEO score

86

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

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 Fcmiamicity.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 Fcmiamicity.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

fcmiamicity.com

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