4.5 sec in total
170 ms
2.7 sec
1.6 sec
Click here to check amazing Esim content. Otherwise, check out these important facts you probably never knew about esim.com
Save on incredible benefits every month. Learn about unlimited plans, 5G internet & more.
Visit esim.comWe analyzed Esim.com page load time and found that the first response time was 170 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
esim.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value7.9 s
3/100
25%
Value5.7 s
52/100
10%
Value9,930 ms
0/100
30%
Value0
100/100
15%
Value24.8 s
0/100
10%
170 ms
55 ms
41 ms
24 ms
46 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Esim.com, 64% (47 requests) were made to T-mobile.com and 33% (24 requests) were made to T-mobile.scene7.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source T-mobile.com.
Page size can be reduced by 451.5 kB (13%)
3.4 MB
2.9 MB
In fact, the total size of Esim.com main page is 3.4 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 2.9 MB which makes up the majority of the site volume.
Potential reduce by 331.1 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 331.1 kB or 87% of the original size.
Potential reduce by 120.4 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. Esim images are well optimized though.
Potential reduce by 0 B
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.
Number of requests can be reduced by 37 (52%)
71
34
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Esim. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
esim.com
170 ms
www.t-mobile.com
55 ms
launch-1df223c5538b.min.js
41 ms
alpinejs.ACSHASH81538a1c899c172bd6426ebea218229d.js
24 ms
js-cookie.ACSHASHf43aa9c402931374e21a578b461f7aa7.js
46 ms
uuid.ACSHASHdc65c89ca61cfbe9d41b884c00228c12.js
108 ms
localforage.ACSHASHee71d112d54790940846b4be5b40bdd8.js
41 ms
fetch.ACSHASHa3ba3124b71515bf2eb6fdb1ae84f294.js
46 ms
clientlib-platform-main.ACSHASH32cd1ec22e4d30aa307956a4df945308.js
45 ms
webvitals.ACSHASHa70b7a345f326b5f9bee7d4ae9b2a770.js
37 ms
global-privacy.ACSHASHd603c62dff790a64ee354e8c1bf1b03d.js
50 ms
authorization.ACSHASHf258f6bda4487c247d2ca9e9adbadfba.js
66 ms
clientlib-grid.ACSHASH6d3dc1c380a0096e0df0b86cf65b1866.css
51 ms
clientlib-experience-main.ACSHASHceb1849156758a56f916882ed0f9132f.css
115 ms
clientlib-tmobile.ACSHASHbf57bd30b9c6c98bc0658ccfaae2c03d.css
59 ms
clientlib-experience-components.ACSHASH7c686594c4746ed969b4b3b92b722381.css
77 ms
clientlib-experience-forms.ACSHASHa4950da55cc3fbd0032a6664039d3345.css
106 ms
clientlib-unav-main.ACSHASH7c087b559159243b6717f46cce9fffe7.css
65 ms
clientlib.ACSHASH2c93cc80b7a6ce636339da2447124ebb.css
71 ms
lodash.ACSHASH1edc1bbf61f1ee47e477fad6c4d17529.js
83 ms
clientlib-experience-utils.ACSHASHc1fc024536dbd990ba9012176c61ae0c.js
86 ms
clientlib.ACSHASH7264e30d76a859ff3e3b265694c75119.js
111 ms
clientlib.ACSHASHa2575137e10dff0b64b472353decc89b.css
90 ms
clientlib.ACSHASH1194e38e88121513bd764ab27a3a064f.js
2267 ms
clientlib.ACSHASH64dbf054891fba4d5a38637f60fb0c54.js
108 ms
clientlib.ACSHASH09411187297d037e902f52914ab08a60.js
2266 ms
clientlib.ACSHASH807d3fb54602e47958f4d00a968a5c8e.css
2259 ms
clientlib.ACSHASHfd4c279c0baef1edc6689f5c8f7364ad.js
2261 ms
clientlib.ACSHASH2ca95ac26f74b45109753753936bece0.css
2260 ms
clientlib.ACSHASH11cd02045b32544cc9acc830de0bb06b.css
2258 ms
clientlib.ACSHASHfe127beaaa3527252b7a33f80bea1748.js
2262 ms
body-scroll-lock.ACSHASH0d4cb47b4e3c59ebadbb51bd0e8ee48d.js
2261 ms
clientlib-experience-main.ACSHASH50b1dc663a332e841105e90f788d2f0c.js
2262 ms
a11y-dialog.ACSHASH614761c4fd546064259ed78c021ca517.js
2260 ms
clientlib-experience-components.ACSHASH73000533bf90c91a4d00f5ce3fba5826.js
2263 ms
iodine.ACSHASHdb5e37dabbd9dc0b0cb6534afb6fb7e4.js
2259 ms
cleave.ACSHASH166bc4015c6b84dac614d4c098f39a53.js
2262 ms
recaptcha.ACSHASHfba611a68c8a75b39412c89c8f34586b.js
2261 ms
leadGen.ACSHASHd10dd33d800db66e828661ede6da6172.js
2262 ms
clientlib-experience-forms.ACSHASH8260784717c5fc93d9910546f1416b3a.js
2258 ms
clientlib-analytics-main.ACSHASHeaba2ef4d8d03e0ba646ac14286527d2.js
2243 ms
fg-iPhone-16-Pro-Smartcrops:4x3
2251 ms
fg-Go5G-Next-Liquid-with-Phone-Freedom-1x1:4x3
419 ms
6169092-50-white-gateway-voice-4
425 ms
fg-iPhone-16-lineup
431 ms
fg-apple-series-10-vertical-1x1
424 ms
5628307_Device-ReTargeting-Banners-iPhone14-PLP-banner-FG-750x750-2
427 ms
FG_Samsung_Galaxy-S24_Amber-Yellow_Hero_NoLogo_750x7501
422 ms
5602450_BG_iPhone15_PEGA-NBA-FG-750x750
425 ms
Kate-Spade_iPhone-16_Cases-1:1x1
433 ms
MTE2-1
435 ms
eyebrow-Go5G-Next-horiz-white
438 ms
6300773-Family-3-on-sailing-boat-with-phone_3000x2000px1:4x3
437 ms
Go5G-Plus-Eyebrow-Rev-2
426 ms
6300773-family-selfie-on-vacation_2122x1500px-1%3A1x1
442 ms
EssSav-Eyebrow-Rev-2
440 ms
6300773-man-sitting-with-phone_2425x1500px1%3AHERO-tablet
499 ms
Magenta-Status-BG%3AHERO-mobile
490 ms
m-status-750x750-fg-minus-intro
489 ms
fg-scamshield-rounded-black
492 ms
Netflix-Eng-Streaming_FG_750x750
493 ms
MultiTile_HP-Benefits-Streaming_FG_750x750-1
517 ms
Shogun_Hulu_Streaming_FG_750x750-1
490 ms
HP_evergreen
494 ms
Roaming-M1-fg-12
498 ms
tmo-logo-v4.svg
365 ms
hsi.jpg
366 ms
icon-tfb-enterprise-750x750.png
364 ms
icon-5G-map-pin.png
363 ms
travel.jpg
365 ms
icon-clapping-hands.png
364 ms
free-trial.jpg
434 ms
tmo-logo-white-v4.svg
415 ms
esim.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
esim.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
esim.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Esim.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 Esim.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.
esim.com
Open Graph data is detected on the main page of Esim. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: