3.2 sec in total
602 ms
2.2 sec
328 ms
Welcome to forums.verizon.com homepage info - get ready to check Forums Verizon best content for United States right away, or after learning these important things about forums.verizon.com
Ask, learn, and discuss products and services with your peers in the Verizon Community
Visit forums.verizon.comWe analyzed Forums.verizon.com page load time and found that the first response time was 602 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
forums.verizon.com performance score
name
value
score
weighting
Value2.7 s
61/100
10%
Value10.7 s
0/100
25%
Value5.6 s
53/100
10%
Value2,810 ms
3/100
30%
Value0.003
100/100
15%
Value32.4 s
0/100
10%
602 ms
166 ms
153 ms
152 ms
230 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 12% of them (12 requests) were addressed to the original Forums.verizon.com, 49% (51 requests) were made to Vrzn.i.lithium.com and 16% (17 requests) were made to Verizon.com. The less responsive or slowest element that took the longest time to load (676 ms) belongs to the original domain Forums.verizon.com.
Page size can be reduced by 708.3 kB (70%)
1.0 MB
308.5 kB
In fact, the total size of Forums.verizon.com main page is 1.0 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. 65% of websites need less resources to load. Javascripts take 404.5 kB which makes up the majority of the site volume.
Potential reduce by 167.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 167.1 kB or 81% of the original size.
Potential reduce by 219.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, Forums Verizon needs image optimization as it can save up to 219.9 kB or 61% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 284.5 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 284.5 kB or 70% of the original size.
Potential reduce by 36.8 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. Forums.verizon.com needs all CSS files to be minified and compressed as it can save up to 36.8 kB or 83% of the original size.
Number of requests can be reduced by 54 (59%)
91
37
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Forums 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 30 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
forums.verizon.com
602 ms
vrzn-439108329.css
166 ms
layout.css
153 ms
vrzn_rotater.js
152 ms
jquery-1.4.2.min.js
230 ms
sas_menu.js
154 ms
lia-scripts-head-min.js
64 ms
commons.js
27 ms
omnicode.js
25 ms
satelliteLib-8df7d93db820b272138ecb04dbe4ed7f5023b893.js
6 ms
common.css
41 ms
myvzres2012.css
42 ms
myvzconsole.js
33 ms
meta
60 ms
oo_js.js
4 ms
lia-scripts-common-min.js
93 ms
lia-scripts-body-min.js
92 ms
InlineLabelEditor.js
149 ms
community_bg.png
44 ms
vzlogo_lg.png
40 ms
icon_help.png
42 ms
facebook_icon.png
42 ms
twitter_icon.png
58 ms
google_plus_icon.png
58 ms
message
59 ms
message
59 ms
message
60 ms
message
64 ms
message
299 ms
community_leader.gif
80 ms
message
81 ms
64x36
87 ms
message
82 ms
message
104 ms
message
170 ms
profile
341 ms
VZ_logo_sm.png
168 ms
64x36
168 ms
message
168 ms
64x36
168 ms
moderator.gif
290 ms
button_lithium_logo.png
289 ms
view_all_arrow.png
168 ms
thumb
172 ms
Forum_banner_3.png
676 ms
dark_circle.png
168 ms
light_circle.png
169 ms
mbox-contents-38b8f99ca10f023c55557c0e31691691b2737750.js
7 ms
rd
17 ms
target.js
36 ms
id
14 ms
ajax
92 ms
ConsumerServlet
188 ms
commongh
171 ms
satellite-56aba57064746d0e510018e8.js
114 ms
page.twitterstreamtaplet:getnewtweets
257 ms
hero-banner.jpg
31 ms
search_box_bg_wide.png
28 ms
content_left.png
29 ms
content_right.png
28 ms
scbressprite.png
26 ms
search_icon.png
74 ms
caret_png.png
65 ms
scbresspriteback.png
65 ms
selected_tab_blue.png
67 ms
unselected_tab_grey.png
67 ms
view_all_arrow.png
67 ms
category_plus.png
67 ms
top_left.png
68 ms
top_right.png
69 ms
bottom_left.png
69 ms
bottom_right.png
70 ms
left_arrow_disabled.png
70 ms
right_arrow.png
73 ms
icon_twitter_stream.png
74 ms
neuehaasgrotesktext.woff
43 ms
neuehaasgrotesktextmedium.woff
28 ms
neuehaasgrotesktextbold.woff
78 ms
neuehaasgroteskdisplaymedium.woff
78 ms
neuehaasgroteskdisplaybold.woff
76 ms
neuehaasgroteskdisplay.woff
77 ms
verizonapex-book-webfont.woff
296 ms
verizonapex-book-webfont.woff
76 ms
verizonapex-medium-webfont.woff
222 ms
verizonapex-medium-webfont.woff
76 ms
VOLPortalLogin
253 ms
omnicodef.js
25 ms
ajax
144 ms
oo_tab.png
15 ms
oo_tab_icon.gif
15 ms
json
20 ms
s73915302653331
15 ms
iframe_ghp.css
42 ms
Bootstrap.js
34 ms
AC_OETags.js
240 ms
iframe_ghp.js
81 ms
omnicode.js
28 ms
serverComponent.php
44 ms
0bdd5928320bb4bae2dde2992af39d35.js
4 ms
f1e26d7395edc40637e975ca102fbbae.js
7 ms
cobrowse.js
5 ms
CobrowseJS.ashx
116 ms
GlanceCobrowseLoader_3.2.0aM.js
67 ms
ssoghfsprite.png
41 ms
forums.verizon.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.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
forums.verizon.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
forums.verizon.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
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forums.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 Forums.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.
forums.verizon.com
Open Graph data is detected on the main page of Forums Verizon. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: