4.4 sec in total
225 ms
2.4 sec
1.8 sec
Click here to check amazing My Verizon content for United States. Otherwise, check out these important facts you probably never knew about myverizon.com
Log in or register your My Verizon account today! You can check your data usage, pay your bills and manage your account without having to go to a Verizon store.
Visit myverizon.comWe analyzed Myverizon.com page load time and found that the first response time was 225 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
myverizon.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value8.2 s
2/100
25%
Value11.5 s
5/100
10%
Value12,090 ms
0/100
30%
Value0.433
22/100
15%
Value37.3 s
0/100
10%
225 ms
72 ms
304 ms
89 ms
131 ms
Our browser made a total of 177 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Myverizon.com, 34% (60 requests) were made to Image.vam.synacor.com.edgesuite.net and 14% (24 requests) were made to Static.coral.synacor.com. The less responsive or slowest element that took the longest time to load (443 ms) relates to the external source Securepubads.g.doubleclick.net.
Page size can be reduced by 1.4 MB (34%)
3.9 MB
2.6 MB
In fact, the total size of Myverizon.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. 85% 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.3 MB which makes up the majority of the site volume.
Potential reduce by 913.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 913.0 kB or 89% of the original size.
Potential reduce by 56.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. My Verizon images are well optimized though.
Potential reduce by 385.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 385.7 kB or 64% of the original size.
Number of requests can be reduced by 44 (28%)
159
115
The browser has sent 159 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Verizon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
myverizon.com
225 ms
entertainment.verizon.com
72 ms
fiostrending.verizon.com
304 ms
res.php
89 ms
res.php
131 ms
res.php
105 ms
commons.js
56 ms
omnicode.js
57 ms
satelliteLib-8df7d93db820b272138ecb04dbe4ed7f5023b893.js
11 ms
common.css
81 ms
myvzres2012.css
80 ms
myvzconsole.js
56 ms
oo_js.js
63 ms
vzTracker.aspx
25 ms
mbox-contents-38b8f99ca10f023c55557c0e31691691b2737750.js
5 ms
vzlogo_lg.png
4 ms
adchoices_icon.png
17 ms
rd
13 ms
target.js
10 ms
id
215 ms
commongh
192 ms
satellite-56dd9d8e64746d0521000570.js
171 ms
48 ms
194 ms
verizon
68 ms
33 ms
analytics.js
30 ms
gpt.js
22 ms
gemini.js
50 ms
outbrain.js
48 ms
119 ms
iframe.html
43 ms
Bootstrap.js
43 ms
track.gif
37 ms
track.gif
38 ms
ajax
41 ms
pubads_impl_82.js
27 ms
verizon
102 ms
postmessage.js
28 ms
bk-coretag.js
26 ms
g-d-min.js
19 ms
ssi
185 ms
serverComponent.php
49 ms
show_companion_ad.js
31 ms
container.html
28 ms
res.php
25 ms
res.php
24 ms
62bf6ee70ec661f9c7ea89d0e10a92a0.js
18 ms
d8f1eb748be2c6ad69c3de00c53f16c1.js
5 ms
powered_by_topix.png
85 ms
208 ms
beacon.js
13 ms
track.gif
16 ms
s93973122129682
83 ms
cb-1445016788490-2099.plain
2 ms
a00efd0cb63f3a8b58fd745b283a6094.jpeg
3 ms
eb2debabd532b8f75154b467945c8e4c.jpeg
26 ms
66d8de70da6880ce017a93d0108cbcfa.jpeg
9 ms
23a31a079112f621e989f875b5f5bc94.jpeg
61 ms
1456144122147-3755.jpg
10 ms
ce2f6c5f0224e15e534bc894721c45b2.jpeg
18 ms
164ef6c3840980ec39623824fc5c9cf2.jpeg
17 ms
02626337586b0b9bf61ddaf2f9385a01.jpeg
132 ms
bdb474fe2d7152b2dacddb45a7a8d39b.jpeg
26 ms
d54039508e2aa4d4e74452621b5a5008.jpeg
23 ms
get
53 ms
1Ja02Q-1G7Y-300x300.jpg
106 ms
1CKwBW-1G7Y-300x300.jpg
98 ms
11XjRd-1G7Y-300x300.jpg
98 ms
1GeRGQ-1G7Y-300x300.jpg
95 ms
1LwUob-1G7Y-300x300.jpg
99 ms
1Lnwjn-1G7Y-300x300.jpg
95 ms
1LniFV-1G7Y-300x300.jpg
96 ms
1MEetl-1G7Y-300x300.jpg
98 ms
ads
443 ms
206 ms
track.gif
83 ms
track.gif
82 ms
comScore.htm
79 ms
scbressprite.png
71 ms
searchproviders.png
65 ms
61 ms
345ddb8a6f7c67df4ef470ac48834f39.jpeg
46 ms
caret_png.png
97 ms
scbresspriteback.png
97 ms
ob_logo_67x12.png
108 ms
syndication@2x.png
95 ms
7f09534d29c63f0406813a143496f54e.jpeg
133 ms
c9e7d1765acd5624def303e656cba0d3.jpeg
110 ms
video-placeholder-tablet.png
132 ms
96 ms
99 ms
100 ms
97 ms
105 ms
97 ms
100 ms
101 ms
108 ms
103 ms
104 ms
105 ms
108 ms
111 ms
110 ms
108 ms
111 ms
112 ms
112 ms
113 ms
114 ms
116 ms
116 ms
116 ms
117 ms
118 ms
119 ms
119 ms
120 ms
120 ms
120 ms
121 ms
121 ms
122 ms
123 ms
117 ms
227 ms
227 ms
227 ms
227 ms
227 ms
226 ms
224 ms
224 ms
225 ms
225 ms
223 ms
223 ms
223 ms
222 ms
221 ms
222 ms
222 ms
221 ms
221 ms
221 ms
220 ms
221 ms
ads
193 ms
track.gif
103 ms
track.gif
102 ms
neuehaasgrotesktextbold.woff
104 ms
neuehaasgrotesktextmedium.woff
102 ms
neuehaasgrotesktext.woff
102 ms
sourcesanspro-regular.svgz
104 ms
sourcesanspro-regular.woff
104 ms
neuehaasgroteskdisplay.woff
226 ms
neuehaasgroteskdisplaymedium.woff
103 ms
neuehaasgroteskdisplaybold.woff
103 ms
symbolset-custom.woff
225 ms
sourcesanspro-semibold.svgz
224 ms
sourcesanspro-semibold.woff
224 ms
sourcesanspro-bold.woff
224 ms
sourcesanspro-light.svgz
223 ms
sourcesanspro-light.woff
353 ms
widgetGlobalEvent
97 ms
widgetGlobalEvent
97 ms
imgad
358 ms
en
306 ms
en
307 ms
en
306 ms
jwplayer.js
303 ms
osd.js
141 ms
sourcesanspro-regular.woff
308 ms
imgad
293 ms
imgad
293 ms
vast.js
131 ms
myverizon.com accessibility score
myverizon.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
myverizon.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 Myverizon.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 Myverizon.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.
myverizon.com
Open Graph description is not detected on the main page of My Verizon. 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: