Tools & Wizards About Us
verizom.com screenshot

Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

verizom.com

Verizon Home Internet & WiFi Service | Verizon

Page Load Speed

2 sec in total

First Response

368 ms

Resources Loaded

1.4 sec

Page Rendered

281 ms

verizom.com screenshot

About Website

Welcome to verizom.com homepage info - get ready to check Verizom best content right away, or after learning these important things about verizom.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 verizom.com

Key Findings

We analyzed Verizom.com page load time and found that the first response time was 368 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

verizom.com performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value14.4 s

0/100

25%

SI (Speed Index)

Value17.3 s

0/100

10%

TBT (Total Blocking Time)

Value14,050 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.376

28/100

15%

TTI (Time to Interactive)

Value43.5 s

0/100

10%

Network Requests Diagram

368 ms

15 ms

launch-e7ddfa510cc0.min.js

56 ms

vztc.js

78 ms

components-base.min.css

19 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Verizom.com, 18% (7 requests) were made to Ss7.vzw.com and 8% (3 requests) were made to Scache1.vzw.com. The less responsive or slowest element that took the longest time to load (517 ms) relates to the external source Ss7.vzw.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 812.5 kB (59%)

Content Size

1.4 MB

After Optimization

567.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Verizom.com main page is 1.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. 50% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 162.9 kB

  • Original 192.6 kB
  • After minification 167.2 kB
  • After compression 29.8 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 25.4 kB, which is 13% 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 162.9 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 76.5 kB
  • After minification 76.5 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. Verizom images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 649.6 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 461.3 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 649.6 kB or 58% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (59%)

Requests Now

32

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

368 ms

15 ms

launch-e7ddfa510cc0.min.js

launch-e7ddfa510cc0.min.js

56 ms

vztc.js

vztc.js

78 ms

components-base.min.css

components-base.min.css

19 ms

jquery.min.js

jquery.min.js

36 ms

utils.min.js

utils.min.js

78 ms

granite.min.js

granite.min.js

43 ms

jquery.min.js

jquery.min.js

41 ms

contexthub.js

contexthub.js

42 ms

index.css

index.css

39 ms

index.css

index.css

40 ms

core.css

core.css

44 ms

personal.js

personal.js

41 ms

manifest.min.js

manifest.min.js

45 ms

vendor-utils.min.js

vendor-utils.min.js

46 ms

vendor.min.js

vendor.min.js

48 ms

components-base.min.js

components-base.min.js

50 ms

tagging.min.js

tagging.min.js

71 ms

sm.min.css

sm.min.css

13 ms

md.min.css

md.min.css

8 ms

lg.min.css

lg.min.css

16 ms

xl.min.css

xl.min.css

4 ms

token.json

token.json

189 ms

contexthub.pagedata.json

contexthub.pagedata.json

80 ms

segments.seg.js

segments.seg.js

79 ms

vhi_promo_update_raybans_on_us_vhi_d

vhi_promo_update_raybans_on_us_vhi_d

434 ms

samsung_appliance_2plusindividualtiles_d

samsung_appliance_2plusindividualtiles_d

434 ms

vhi_home_hub_vz_gc_d

vhi_home_hub_vz_gc_d

433 ms

raybans_modal_vhi_promo_modal_d

raybans_modal_vhi_promo_modal_d

434 ms

samsung_appliance_promomodal_d

samsung_appliance_promomodal_d

434 ms

vhi-fall-promos-giftcard-d

vhi-fall-promos-giftcard-d

517 ms

raybans_modal_fios_tile_promo_modal_d

raybans_modal_fios_tile_promo_modal_d

457 ms

VerizonNHGeTX-Bold.woff

VerizonNHGeTX-Bold.woff

377 ms

VerizonNHGeTX-Regular.woff

VerizonNHGeTX-Regular.woff

400 ms

VerizonNHGeDS-Regular.woff

VerizonNHGeDS-Regular.woff

401 ms

VerizonNHGeDS-Bold.woff

VerizonNHGeDS-Bold.woff

432 ms

VerizonNHGDS-Light.woff

VerizonNHGDS-Light.woff

334 ms

gNavRibbon.model.isActive:true.json

gNavRibbon.model.isActive:true.json

229 ms

Accessibility Review

verizom.com accessibility score

88

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

High

[aria-*] attributes do not have valid values

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

verizom.com best practices score

75

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

Missing source maps for large first-party JavaScript

SEO Factors

verizom.com SEO score

86

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

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

verizom.com

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