Tools & Wizards About Us
suncom.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

suncom.com

T-Mobile® Official Site: Get Even More Without Paying More | T-Mobile & Sprint Merged to Give You More

Page Load Speed

4.1 sec in total

First Response

266 ms

Resources Loaded

3.5 sec

Page Rendered

358 ms

suncom.com screenshot

About Website

Click here to check amazing Suncom content. Otherwise, check out these important facts you probably never knew about suncom.com

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

Visit suncom.com

Key Findings

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

Performance Metrics

suncom.com performance score

0

Network Requests Diagram

suncom.com

266 ms

www.t-mobile.com

255 ms

launch-31a1bb9770e3.min.js

245 ms

clientlib-at-body-hider.ACSHASHfaebaeb770169611ecfc78f0525976ce.css

95 ms

clientlib-at-body-hider.ACSHASHc83c03ef185d8832a48fd34968be6fa5.js

131 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Suncom.com, 94% (44 requests) were made to T-mobile.com and 2% (1 request) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (514 ms) relates to the external source T-mobile.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 240.5 kB (78%)

Content Size

308.0 kB

After Optimization

67.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Suncom.com main page is 308.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. HTML takes 275.9 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 237.9 kB

  • Original 275.9 kB
  • After minification 252.8 kB
  • After compression 38.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. 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 237.9 kB or 86% of the original size.

Image Optimization

-22%

Potential reduce by 2.5 kB

  • Original 11.4 kB
  • After minification 8.9 kB

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. Obviously, Suncom needs image optimization as it can save up to 2.5 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 20 B

  • Original 20.6 kB
  • After minification 20.6 kB
  • After compression 20.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. This website has mostly compressed JavaScripts.

Requests Breakdown

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

Requests Now

45

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

suncom.com

suncom.com

266 ms

www.t-mobile.com

www.t-mobile.com

255 ms

launch-31a1bb9770e3.min.js

launch-31a1bb9770e3.min.js

245 ms

clientlib-at-body-hider.ACSHASHfaebaeb770169611ecfc78f0525976ce.css

clientlib-at-body-hider.ACSHASHfaebaeb770169611ecfc78f0525976ce.css

95 ms

clientlib-at-body-hider.ACSHASHc83c03ef185d8832a48fd34968be6fa5.js

clientlib-at-body-hider.ACSHASHc83c03ef185d8832a48fd34968be6fa5.js

131 ms

webvitals.ACSHASHae6aaefc6ff7d5aae0aac02adf7a6efb.js

webvitals.ACSHASHae6aaefc6ff7d5aae0aac02adf7a6efb.js

131 ms

alpinejs.ACSHASHbd14e35fa65fb7ddca1fbb85ef7474e3.js

alpinejs.ACSHASHbd14e35fa65fb7ddca1fbb85ef7474e3.js

130 ms

js-cookie.ACSHASHd82efb970b8c4a20dd6caeb0c91a0ac8.js

js-cookie.ACSHASHd82efb970b8c4a20dd6caeb0c91a0ac8.js

130 ms

uuid.ACSHASH521436ff0c6875d874e709cd7968ad61.js

uuid.ACSHASH521436ff0c6875d874e709cd7968ad61.js

130 ms

localforage.ACSHASH99f15e55d7b83adb75ea1de950603ddd.js

localforage.ACSHASH99f15e55d7b83adb75ea1de950603ddd.js

129 ms

fetch.ACSHASHd364ab67e3b5b0477feb146d0b2bf80f.js

fetch.ACSHASHd364ab67e3b5b0477feb146d0b2bf80f.js

160 ms

clientlib-platform-main.ACSHASH84cd662cd7b381582e2bec44647ace14.js

clientlib-platform-main.ACSHASH84cd662cd7b381582e2bec44647ace14.js

143 ms

authorization.ACSHASH0fd2ff80ce78ec1195910b31968f95e1.js

authorization.ACSHASH0fd2ff80ce78ec1195910b31968f95e1.js

159 ms

clientlib-grid.ACSHASH1b5d6c727f68d3010014f4f355f908eb.css

clientlib-grid.ACSHASH1b5d6c727f68d3010014f4f355f908eb.css

158 ms

clientlib-experience-main.ACSHASHfa85a6b18b921bdb8666bab7bf2ef7f6.css

clientlib-experience-main.ACSHASHfa85a6b18b921bdb8666bab7bf2ef7f6.css

240 ms

clientlib-tmobile.ACSHASH42fb0f53549714500750aa69d456df5b.css

clientlib-tmobile.ACSHASH42fb0f53549714500750aa69d456df5b.css

158 ms

clientlib-experience-components.ACSHASH6073e16f8e3000835d7ff5faa1d4f181.css

clientlib-experience-components.ACSHASH6073e16f8e3000835d7ff5faa1d4f181.css

213 ms

clientlib-experience-forms.ACSHASHc58cff6f7cd2bf58dbb39bf0814a306d.css

clientlib-experience-forms.ACSHASHc58cff6f7cd2bf58dbb39bf0814a306d.css

213 ms

clientlib-main.ACSHASH7d59afdb1c50073e9a3761f53fb7eb83.css

clientlib-main.ACSHASH7d59afdb1c50073e9a3761f53fb7eb83.css

207 ms

clientlib.ACSHASH3d07057a9b1f8b42cdfeb36c6720a7fc.css

clientlib.ACSHASH3d07057a9b1f8b42cdfeb36c6720a7fc.css

207 ms

clientlib.ACSHASH90681aa62ef6bc6b472a26b5fe2028b2.css

clientlib.ACSHASH90681aa62ef6bc6b472a26b5fe2028b2.css

207 ms

clientlib.ACSHASHc8822ddf26dd5e9659bc648ca741acdf.js

clientlib.ACSHASHc8822ddf26dd5e9659bc648ca741acdf.js

233 ms

lodash.ACSHASHaa6d8730be3275a44c50d8d50809b2d6.js

lodash.ACSHASHaa6d8730be3275a44c50d8d50809b2d6.js

232 ms

clientlib-experience-utils.ACSHASHf85ed0ca3c440494cb405e3695695b9b.js

clientlib-experience-utils.ACSHASHf85ed0ca3c440494cb405e3695695b9b.js

231 ms

clientlib.ACSHASH477db7ba9a4ffe1c035e5fa2621d9b4e.js

clientlib.ACSHASH477db7ba9a4ffe1c035e5fa2621d9b4e.js

232 ms

clientlib.ACSHASH16e065dac68d3f04a8e1bfa6a4c20a27.js

clientlib.ACSHASH16e065dac68d3f04a8e1bfa6a4c20a27.js

231 ms

a11y-dialog.ACSHASH615db03fbf199df48c3f42f06c03ac14.js

a11y-dialog.ACSHASH615db03fbf199df48c3f42f06c03ac14.js

404 ms

body-scroll-lock.ACSHASH8d9f4b0627dd89b99a35b9dd8c9993eb.js

body-scroll-lock.ACSHASH8d9f4b0627dd89b99a35b9dd8c9993eb.js

403 ms

clientlib.ACSHASHc9a5e34b3278f180ad077bcaba92a946.js

clientlib.ACSHASHc9a5e34b3278f180ad077bcaba92a946.js

403 ms

clientlib.ACSHASHccdae4b9ba6e0973952aa4dfc32a960a.css

clientlib.ACSHASHccdae4b9ba6e0973952aa4dfc32a960a.css

403 ms

clientlib.ACSHASHf11ff81f65ce28c38e9c3c6a8c270c6c.css

clientlib.ACSHASHf11ff81f65ce28c38e9c3c6a8c270c6c.css

401 ms

clientlib.ACSHASH3ae4dc378dd82eda6a1130961dacdd27.css

clientlib.ACSHASH3ae4dc378dd82eda6a1130961dacdd27.css

426 ms

clientlib.ACSHASHdb88376259522231dad9c583413cf0a3.js

clientlib.ACSHASHdb88376259522231dad9c583413cf0a3.js

514 ms

lazysizes.ACSHASH0e71b52c15cc97c48252537cce85abab.js

lazysizes.ACSHASH0e71b52c15cc97c48252537cce85abab.js

513 ms

clientlib-experience-components.ACSHASH4d161aab329c53107707df332c16f960.js

clientlib-experience-components.ACSHASH4d161aab329c53107707df332c16f960.js

475 ms

iodine.ACSHASH93fb60043a13ffd1707c56601c00d3e2.js

iodine.ACSHASH93fb60043a13ffd1707c56601c00d3e2.js

473 ms

cleave.ACSHASHe7bb62d4061003340d06e21e6cf9594a.js

cleave.ACSHASHe7bb62d4061003340d06e21e6cf9594a.js

471 ms

clientlib-experience-forms.ACSHASH906a1d96d23f5c2c1f8d62ff42a8c117.js

clientlib-experience-forms.ACSHASH906a1d96d23f5c2c1f8d62ff42a8c117.js

474 ms

clientlib-analytics-main.ACSHASH05b2903ebe2efd530946fedac6a18b34.js

clientlib-analytics-main.ACSHASH05b2903ebe2efd530946fedac6a18b34.js

510 ms

_Incapsula_Resource

_Incapsula_Resource

495 ms

bg-bora-4

bg-bora-4

298 ms

tmo-logo-v4.svg

tmo-logo-v4.svg

184 ms

icons.svg

icons.svg

206 ms

cta-apple-app-store-icon-150x45.png

cta-apple-app-store-icon-150x45.png

186 ms

cta-google-play-store-icon-150x45.png

cta-google-play-store-icon-150x45.png

182 ms

tmo-logo-white-v4.svg

tmo-logo-white-v4.svg

184 ms

_Incapsula_Resource

_Incapsula_Resource

9 ms

SEO Factors

suncom.com SEO score

0

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

suncom.com

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