Tools & Wizards About Us
uncarrier.t-mobile.com screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

uncarrier.t-mobile.com

T-Mobile® Official Site: Get Even More Without Paying More

Page Load Speed

3.1 sec in total

First Response

40 ms

Resources Loaded

1.9 sec

Page Rendered

1.1 sec

uncarrier.t-mobile.com screenshot

About Website

Welcome to uncarrier.t-mobile.com homepage info - get ready to check Uncarrier T Mobile best content for United States right away, or after learning these important things about uncarrier.t-mobile.com

Save on incredible benefits every month. Learn about unlimited plans, 5G internet & more.

Visit uncarrier.t-mobile.com

Key Findings

We analyzed Uncarrier.t-mobile.com page load time and found that the first response time was 40 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

uncarrier.t-mobile.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value2,170 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.3 s

2/100

10%

Network Requests Diagram

www.t-mobile.com

40 ms

launch-1df223c5538b.min.js

26 ms

alpinejs.ACSHASHd2728c9cce54144b71c50210bddbbbee.js

16 ms

js-cookie.ACSHASH36b75f405306acfba42bfd1e232acb78.js

28 ms

uuid.ACSHASHeab3529dfc41c0244b78bc53cef21ed9.js

31 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Uncarrier.t-mobile.com, 34% (25 requests) were made to T-mobile.scene7.com and 1% (1 request) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source T-mobile.scene7.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 392.4 kB (16%)

Content Size

2.5 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Uncarrier.t-mobile.com main page is 2.5 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. 65% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 332.7 kB

  • Original 382.7 kB
  • After minification 341.5 kB
  • After compression 50.0 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 41.2 kB, which is 11% 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 332.7 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 41.8 kB

  • Original 2.0 MB
  • After minification 2.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. Uncarrier T Mobile images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 17.9 kB

  • Original 105.2 kB
  • After minification 105.2 kB
  • After compression 87.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 17.9 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (52%)

Requests Now

73

After Optimization

35

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.t-mobile.com

www.t-mobile.com

40 ms

launch-1df223c5538b.min.js

launch-1df223c5538b.min.js

26 ms

alpinejs.ACSHASHd2728c9cce54144b71c50210bddbbbee.js

alpinejs.ACSHASHd2728c9cce54144b71c50210bddbbbee.js

16 ms

js-cookie.ACSHASH36b75f405306acfba42bfd1e232acb78.js

js-cookie.ACSHASH36b75f405306acfba42bfd1e232acb78.js

28 ms

uuid.ACSHASHeab3529dfc41c0244b78bc53cef21ed9.js

uuid.ACSHASHeab3529dfc41c0244b78bc53cef21ed9.js

31 ms

localforage.ACSHASH07df3c3b2a00d863bd93c888a0cb852e.js

localforage.ACSHASH07df3c3b2a00d863bd93c888a0cb852e.js

32 ms

fetch.ACSHASH25501b28f49a5a2a341c672bead80b93.js

fetch.ACSHASH25501b28f49a5a2a341c672bead80b93.js

32 ms

clientlib-platform-main.ACSHASH6c93cb854b7691928cb776d9d5d59e60.js

clientlib-platform-main.ACSHASH6c93cb854b7691928cb776d9d5d59e60.js

55 ms

webvitals.ACSHASH9a5af313a42632e0b9c9a0d329acf9b1.js

webvitals.ACSHASH9a5af313a42632e0b9c9a0d329acf9b1.js

31 ms

global-privacy.ACSHASH57d32d90f0f659ab55c86d08a5c21f45.js

global-privacy.ACSHASH57d32d90f0f659ab55c86d08a5c21f45.js

46 ms

authorization.ACSHASH613d69ca41733315d91e695fdeb7963a.js

authorization.ACSHASH613d69ca41733315d91e695fdeb7963a.js

55 ms

clientlib-grid.ACSHASH23c3b28b9ed391c428586dd2cddbee30.css

clientlib-grid.ACSHASH23c3b28b9ed391c428586dd2cddbee30.css

38 ms

clientlib-experience-main.ACSHASHd644730dbc2da863996468bdad747c88.css

clientlib-experience-main.ACSHASHd644730dbc2da863996468bdad747c88.css

40 ms

clientlib-tmobile.ACSHASH322934596a20a7e2bcec3761242420e1.css

clientlib-tmobile.ACSHASH322934596a20a7e2bcec3761242420e1.css

38 ms

clientlib-experience-components.ACSHASH1b7aa5b8ee2aff007cc10491a10138fa.css

clientlib-experience-components.ACSHASH1b7aa5b8ee2aff007cc10491a10138fa.css

49 ms

clientlib-experience-forms.ACSHASH6a7f205162b34ac85b106df1b5d8d5e9.css

clientlib-experience-forms.ACSHASH6a7f205162b34ac85b106df1b5d8d5e9.css

63 ms

5331c9ad

5331c9ad

192 ms

clientlib-unav-main.ACSHASHaf71054af4f61517057a1784a8638917.css

clientlib-unav-main.ACSHASHaf71054af4f61517057a1784a8638917.css

55 ms

clientlib.ACSHASH614e2334d722b52e9c353817aa3d5b10.css

clientlib.ACSHASH614e2334d722b52e9c353817aa3d5b10.css

58 ms

lodash.ACSHASHe6324da83e365651034e6d4ee304d969.js

lodash.ACSHASHe6324da83e365651034e6d4ee304d969.js

107 ms

clientlib-experience-utils.ACSHASH0ab9c238d96a8d9c3a0ed7bc2a6ba321.js

clientlib-experience-utils.ACSHASH0ab9c238d96a8d9c3a0ed7bc2a6ba321.js

106 ms

clientlib.ACSHASH7ece019b9007f563bb70249c9c941c54.js

clientlib.ACSHASH7ece019b9007f563bb70249c9c941c54.js

312 ms

clientlib.ACSHASH4c53a404f74a7a12c744a459d1f72096.css

clientlib.ACSHASH4c53a404f74a7a12c744a459d1f72096.css

85 ms

clientlib.ACSHASH104feca0dbc070eee4ede7bdeb85f557.js

clientlib.ACSHASH104feca0dbc070eee4ede7bdeb85f557.js

106 ms

clientlib.ACSHASH0d086fa01f670cd715be53f758986de2.js

clientlib.ACSHASH0d086fa01f670cd715be53f758986de2.js

106 ms

clientlib.ACSHASHde669151994c10c7233ca886b7dc4566.js

clientlib.ACSHASHde669151994c10c7233ca886b7dc4566.js

106 ms

clientlib.ACSHASH5e6ee4dd2c54ea55c824dbf0d063f42d.css

clientlib.ACSHASH5e6ee4dd2c54ea55c824dbf0d063f42d.css

102 ms

clientlib.ACSHASH3dff2cd7d35aa9deb7c419845958f2d5.js

clientlib.ACSHASH3dff2cd7d35aa9deb7c419845958f2d5.js

162 ms

clientlib.ACSHASHc5596ce9faab3d7fc6cc51a27f1da7af.css

clientlib.ACSHASHc5596ce9faab3d7fc6cc51a27f1da7af.css

115 ms

clientlib.ACSHASHa51df84edb22e0ab8863549546419390.css

clientlib.ACSHASHa51df84edb22e0ab8863549546419390.css

138 ms

clientlib.ACSHASH4089f6c409b77aacfd1a7769dbaee9e8.js

clientlib.ACSHASH4089f6c409b77aacfd1a7769dbaee9e8.js

161 ms

body-scroll-lock.ACSHASH8eb415a9affd113243b2570ea40f434f.js

body-scroll-lock.ACSHASH8eb415a9affd113243b2570ea40f434f.js

162 ms

clientlib-experience-main.ACSHASHe78af188aa7c0d986f6eb7270efe6d04.js

clientlib-experience-main.ACSHASHe78af188aa7c0d986f6eb7270efe6d04.js

162 ms

a11y-dialog.ACSHASH1c6636c0088bd26b85380e6d165363ec.js

a11y-dialog.ACSHASH1c6636c0088bd26b85380e6d165363ec.js

162 ms

clientlib-experience-components.ACSHASH98fb0ceb767d1a73675c1aec7ca6ea42.js

clientlib-experience-components.ACSHASH98fb0ceb767d1a73675c1aec7ca6ea42.js

185 ms

iodine.ACSHASH8bd339f6b07bfcd52ef7df16d892fd10.js

iodine.ACSHASH8bd339f6b07bfcd52ef7df16d892fd10.js

184 ms

cleave.ACSHASH5dfebfea8b0a29db680912f569ef6e89.js

cleave.ACSHASH5dfebfea8b0a29db680912f569ef6e89.js

184 ms

recaptcha.ACSHASHdff4b9a251ad3945ce1f6b57002f0b5b.js

recaptcha.ACSHASHdff4b9a251ad3945ce1f6b57002f0b5b.js

184 ms

leadGen.ACSHASH60b2d8443a9b372578a1e0de993593a1.js

leadGen.ACSHASH60b2d8443a9b372578a1e0de993593a1.js

306 ms

clientlib-experience-forms.ACSHASHfe57969e6b34a7088c60782804149292.js

clientlib-experience-forms.ACSHASHfe57969e6b34a7088c60782804149292.js

290 ms

clientlib-analytics-main.ACSHASH5c6472ddfb65ee8cf5b2cddff1507705.js

clientlib-analytics-main.ACSHASH5c6472ddfb65ee8cf5b2cddff1507705.js

298 ms

fg-iPhone-i5-lineup-4x3-2:HERO-tablet

fg-iPhone-i5-lineup-4x3-2:HERO-tablet

245 ms

bg-family-with-phone

bg-family-with-phone

245 ms

fg-google-g-logo-30px-1-1

fg-google-g-logo-30px-1-1

259 ms

FG_Google_Pixel_9_Pro_no_logo_t_shot_750x7501

FG_Google_Pixel_9_Pro_no_logo_t_shot_750x7501

265 ms

iphone15_fg_750x750-2

iphone15_fg_750x750-2

262 ms

6169092-50-black-gateway-voice-2

6169092-50-black-gateway-voice-2

260 ms

FG-Samsung-Flip6-no-logo

FG-Samsung-Flip6-no-logo

267 ms

FG-Samsung-Fold6-no-logo

FG-Samsung-Fold6-no-logo

260 ms

fg-up-to-800-black-1

fg-up-to-800-black-1

286 ms

Apple-iPhone-14-Yellow-3

Apple-iPhone-14-Yellow-3

293 ms

MTE2-1

MTE2-1

294 ms

eyebrow-Go5G-Next-horiz-white

eyebrow-Go5G-Next-horiz-white

271 ms

6300773-Family-3-on-sailing-boat-with-phone_3000x2000px1:4x3

6300773-Family-3-on-sailing-boat-with-phone_3000x2000px1:4x3

279 ms

Go5G-Plus-Eyebrow-Rev-2

Go5G-Plus-Eyebrow-Rev-2

281 ms

6300773-family-selfie-on-vacation_2122x1500px-1%3A1x1

6300773-family-selfie-on-vacation_2122x1500px-1%3A1x1

1386 ms

EssSav-Eyebrow-Rev-2

EssSav-Eyebrow-Rev-2

294 ms

6300773-man-sitting-with-phone_2425x1500px1%3AHERO-tablet

6300773-man-sitting-with-phone_2425x1500px1%3AHERO-tablet

299 ms

Magenta-Status-BG%3AHERO-mobile

Magenta-Status-BG%3AHERO-mobile

299 ms

m-status-750x750-fg-minus-intro

m-status-750x750-fg-minus-intro

308 ms

fg-scamshield-rounded-black

fg-scamshield-rounded-black

304 ms

Netflix-Eng-Streaming_FG_750x750

Netflix-Eng-Streaming_FG_750x750

306 ms

MultiTile_HP-Benefits-Streaming_FG_750x750-1

MultiTile_HP-Benefits-Streaming_FG_750x750-1

331 ms

Shogun_Hulu_Streaming_FG_750x750-1

Shogun_Hulu_Streaming_FG_750x750-1

317 ms

HP_evergreen

HP_evergreen

318 ms

Roaming-M1-fg-12

Roaming-M1-fg-12

343 ms

tmo-logo-v4.svg

tmo-logo-v4.svg

243 ms

hsi.jpg

hsi.jpg

231 ms

icon-tfb-enterprise-750x750.png

icon-tfb-enterprise-750x750.png

233 ms

icon-5G-map-pin.png

icon-5G-map-pin.png

244 ms

travel.jpg

travel.jpg

243 ms

icon-clapping-hands.png

icon-clapping-hands.png

242 ms

free-trial.jpg

free-trial.jpg

243 ms

tmo-logo-white-v4.svg

tmo-logo-white-v4.svg

307 ms

Accessibility Review

uncarrier.t-mobile.com accessibility score

93

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

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

uncarrier.t-mobile.com best practices score

92

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

Page has valid source maps

SEO Factors

uncarrier.t-mobile.com SEO score

93

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 Uncarrier.t-mobile.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 Uncarrier.t-mobile.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

uncarrier.t-mobile.com

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