Tools & Wizards About Us
auth.verizon.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

auth.verizon.com

Verizon Home Internet & WiFi Service | Verizon

Page Load Speed

4 sec in total

First Response

323 ms

Resources Loaded

2.6 sec

Page Rendered

1.1 sec

auth.verizon.com screenshot

About Website

Click here to check amazing Auth Verizon content for United States. Otherwise, check out these important facts you probably never knew about auth.verizon.com

Get ultra-fast 5G Home, LTE Home or Fios Home Internet with Verizon. Plus, get an Xbox on us, with select plans. Learn more today.

Visit auth.verizon.com

Key Findings

We analyzed Auth.verizon.com page load time and found that the first response time was 323 ms and then it took 3.7 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

auth.verizon.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value30.5 s

0/100

25%

SI (Speed Index)

Value17.9 s

0/100

10%

TBT (Total Blocking Time)

Value12,100 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.083

94/100

15%

TTI (Time to Interactive)

Value50.9 s

0/100

10%

Network Requests Diagram

323 ms

verizon-atom-responsive.min.cfaf2c913a3ae89a23e12b193c2bb2b7.css

69 ms

learn.min.af6213d64092c45c54c3b161f199fdd5.css

179 ms

fiveglearn.min.d37485218ec0401ce58c73d158f13cd6.css

278 ms

vztc.js

549 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Auth.verizon.com, 7% (2 requests) were made to Respframework.verizon.com and 7% (2 requests) were made to Scache2.vzw.com. The less responsive or slowest element that took the longest time to load (999 ms) relates to the external source Scache2.vzw.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 253.1 kB (44%)

Content Size

579.7 kB

After Optimization

326.6 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Auth.verizon.com main page is 579.7 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. 65% of websites need less resources to load. Javascripts take 273.4 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 126.2 kB

  • Original 146.3 kB
  • After minification 110.7 kB
  • After compression 20.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. This page needs HTML code to be minified as it can gain 35.6 kB, which is 24% 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 126.2 kB or 86% of the original size.

JavaScript Optimization

-0%

Potential reduce by 444 B

  • Original 273.4 kB
  • After minification 273.4 kB
  • After compression 272.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

-79%

Potential reduce by 126.5 kB

  • Original 160.0 kB
  • After minification 34.1 kB
  • After compression 33.6 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. Auth.verizon.com needs all CSS files to be minified and compressed as it can save up to 126.5 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (77%)

Requests Now

22

After Optimization

5

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Auth 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 8 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

323 ms

verizon-atom-responsive.min.cfaf2c913a3ae89a23e12b193c2bb2b7.css

verizon-atom-responsive.min.cfaf2c913a3ae89a23e12b193c2bb2b7.css

69 ms

learn.min.af6213d64092c45c54c3b161f199fdd5.css

learn.min.af6213d64092c45c54c3b161f199fdd5.css

179 ms

fiveglearn.min.d37485218ec0401ce58c73d158f13cd6.css

fiveglearn.min.d37485218ec0401ce58c73d158f13cd6.css

278 ms

vztc.js

vztc.js

549 ms

satelliteLib-8df7d93db820b272138ecb04dbe4ed7f5023b893.js

satelliteLib-8df7d93db820b272138ecb04dbe4ed7f5023b893.js

642 ms

core.css

core.css

396 ms

vzlqwidget.js

vzlqwidget.js

589 ms

components.css

components.css

336 ms

index.css

index.css

353 ms

index.css

index.css

353 ms

index.css

index.css

371 ms

personal.js

personal.js

382 ms

learn.min.b54bfeb678d9a452919058d15274cbda.js

learn.min.b54bfeb678d9a452919058d15274cbda.js

571 ms

fiveglearn.min.4080f007c5c213db14ef45adbe641815.js

fiveglearn.min.4080f007c5c213db14ef45adbe641815.js

411 ms

index.js

index.js

411 ms

home.js

home.js

430 ms

app.css

app.css

141 ms

VZ-White.svg

VZ-White.svg

120 ms

fonts.css

fonts.css

202 ms

fonts.css

fonts.css

203 ms

VerizonNHGeTX-Bold.woff

VerizonNHGeTX-Bold.woff

831 ms

VerizonNHGeTX-Regular.woff

VerizonNHGeTX-Regular.woff

427 ms

VerizonNHGeDS-Regular.woff

VerizonNHGeDS-Regular.woff

825 ms

VerizonNHGeDS-Bold.woff

VerizonNHGeDS-Bold.woff

999 ms

homeprospect.external.html

homeprospect.external.html

245 ms

homeprospect.external.html

homeprospect.external.html

196 ms

NeueHaasGroteskTextW02.woff

NeueHaasGroteskTextW02.woff

470 ms

NHaasGroteskDSW02-75Bd.woff

NHaasGroteskDSW02-75Bd.woff

468 ms

Accessibility Review

auth.verizon.com accessibility score

100

Accessibility Issues

Best Practices

auth.verizon.com best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

auth.verizon.com SEO score

93

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

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 Auth.verizon.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 Auth.verizon.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

auth.verizon.com

Open Graph description is not detected on the main page of Auth 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: