76.5 sec in total
571 ms
63.3 sec
12.6 sec
Visit symantec.com now to see the best up-to-date Symantec content for United States and also check out these interesting facts you probably never knew about symantec.com
To meet today's Cyber Security challenges, enterprises need an integrated cyber defense platform that integrates industry-leading solutions and solves for the most pressing C-level challenges like...
Visit symantec.comWe analyzed Symantec.com page load time and found that the first response time was 571 ms and then it took 76 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
symantec.com performance score
name
value
score
weighting
Value2.1 s
81/100
10%
Value9.5 s
0/100
25%
Value7.4 s
27/100
10%
Value1,010 ms
27/100
30%
Value0.018
100/100
15%
Value9.1 s
33/100
10%
571 ms
194 ms
2628 ms
2268 ms
1211 ms
Our browser made a total of 161 requests to load all elements on the main page. We found that 26% of them (42 requests) were addressed to the original Symantec.com, 9% (15 requests) were made to D.adroll.com and 5% (8 requests) were made to Nexus.ensighten.com. The less responsive or slowest element that took the longest time to load (18.4 sec) relates to the external source Facebook.com.
Page size can be reduced by 2.3 MB (16%)
14.3 MB
12.0 MB
In fact, the total size of Symantec.com main page is 14.3 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. 60% of websites need less resources to load. Images take 12.1 MB which makes up the majority of the site volume.
Potential reduce by 79.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. This page needs HTML code to be minified as it can gain 16.0 kB, which is 16% 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 79.0 kB or 80% of the original size.
Potential reduce by 666.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. Symantec images are well optimized though.
Potential reduce by 1.3 MB
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 1.3 MB or 71% of the original size.
Potential reduce by 274.7 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. Symantec.com needs all CSS files to be minified and compressed as it can save up to 274.7 kB or 84% of the original size.
Number of requests can be reduced by 107 (78%)
138
31
The browser has sent 138 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Symantec. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 64 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.symantec.com
571 ms
mbox.js
194 ms
Bootstrap.js
2628 ms
font-awesome.min.css
2268 ms
clientlib.min.css
1211 ms
clientlib.min.css
1444 ms
jquery.min.js
1444 ms
utils.min.js
1443 ms
granite.min.js
1442 ms
jquery.min.js
1443 ms
shared.min.js
1442 ms
underscore.min.js
1823 ms
kernel.min.js
2168 ms
headContainer.min.js
1823 ms
loginAES.min.js
1823 ms
menugroupEndUserFacing.min.js
1765 ms
FlyoutDynamicChange.min.js
1765 ms
hero6633.min.js
2172 ms
customstacking-columncontrol.min.css
2171 ms
cookieredirect.min.js
2172 ms
clientlib.min.js
2171 ms
getseal
2496 ms
s_code_sym.js
2481 ms
clientlib.min.js
2518 ms
target.js
2140 ms
id
3142 ms
serverComponent.php
627 ms
tracker.js
1325 ms
symantec-logo-top.png
1489 ms
endpoint-hybrid-cloud-security-icon.svg
1199 ms
information-protection-icon.svg
1196 ms
web-cloud-security-icon.svg
1323 ms
messaging-security-icon.svg
1325 ms
cyber-security-services-icon.svg
2180 ms
website-security-icon.svg
2125 ms
try-now-icon.svg
2669 ms
service-support-icon.svg
2260 ms
training-certification-icon.svg
2135 ms
events-icon.svg
2975 ms
symantec-logo-footer.png
3021 ms
dest5.html
3425 ms
id
3603 ms
dc2d63dc3443d819822f83f2c1f9cfcf.js
457 ms
2d358f02cf22e4d20eefe44711da482e.js
155 ms
1d5b28d3bf91ed3828f61ae07e1fda36.js
80 ms
86c4bd7a8b8b5ef0251985d25a7c1783.js
551 ms
05d7b82466cc6191303d8d0ae8408f1f.js
553 ms
67f2b9d2df723c16f9ef0df6cbe5bb52.js
552 ms
4c75f345-30fd-46c4-88a4-bef72ca296e2.js
1300 ms
ibs:dpid=411&dpuuid=Wa62AgAAAurnkMd4
398 ms
dpx.js
3840 ms
px.js
4198 ms
bombora.js
6031 ms
VisitorTrack.js
5947 ms
dpx.js
3769 ms
up_loader.1.1.0.js
4738 ms
4c75f345-30fd-46c4-88a4-bef72ca296e2.js
628 ms
WR-latest.js
3322 ms
fbevents.js
4998 ms
fontawesome-webfont.woff
4538 ms
icon-alert.png
2609 ms
ghp-secure-cloud-generation-hero.jpg
2804 ms
ArticulatCF-Text.woff
2188 ms
williams-ghp-slate.jpg
2187 ms
p
1629 ms
ChangeMonitor-latest.js
1373 ms
oct.js
1516 ms
pixel
1551 ms
dpx
1020 ms
214382478902099
912 ms
tag.aspx
1610 ms
dpx
441 ms
pixel
79 ms
adsct
16295 ms
jquery.mousewheel.min.js
14331 ms
18355 ms
bluekai
15465 ms
getseal
13128 ms
utsync.ashx
12985 ms
s65649620860349
14027 ms
jquery.mousewheel.min.js
12346 ms
displaystatus
7291 ms
adsct
8643 ms
prodcutazsearch
5243 ms
activityi;src=6261791;type=mainh0;cat=syman0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=8292862584348.768
7114 ms
193b59e0.min.js
8288 ms
bk-coretag.js
7484 ms
js
8101 ms
elqCfg.min.js
8384 ms
imsync.ashx
5287 ms
sync
8467 ms
CD29559E04B6AE59AA5C9F800203F071
8407 ms
SAML2
9527 ms
csync.ashx
3032 ms
cw_match
2558 ms
rb_match
2290 ms
insight.min.js
9439 ms
ect.html
8952 ms
ip.json
8747 ms
395886.gif
3344 ms
mapuser
3428 ms
common.js
2962 ms
util.js
5495 ms
geocoder.js
7023 ms
rtset
9899 ms
y_match
4542 ms
tpid=CD29559E04B6AE59AA5C9F800203F071
4454 ms
Pug
9062 ms
19857
4053 ms
saml_login
4695 ms
6838 ms
displaystatus
3380 ms
csync.ashx
6654 ms
engine
3767 ms
merge
3245 ms
stats.js
2736 ms
adsct
1960 ms
AuthenticationService.Authenticate
4074 ms
GeocodeService.Search
4156 ms
attr.ml-api.io
3803 ms
pixel
2103 ms
pixel
1965 ms
SAML2
3813 ms
svrGP.aspx
1477 ms
svrGP.aspx
1122 ms
merge
597 ms
tap.php
995 ms
sd
995 ms
1901 ms
aa_px
643 ms
exelate
536 ms
liveramp_sync.xgi
922 ms
4722
741 ms
roundtrip.js
423 ms
W6W7F7RMIBGE7BTUQFVAYL.js
24 ms
out
843 ms
1657297107849740
804 ms
out
1202 ms
out
1242 ms
out
1241 ms
out
1241 ms
out
1242 ms
out
1242 ms
out
1360 ms
out
1698 ms
out
1380 ms
out
1638 ms
out
1637 ms
out
1637 ms
tap.php
1265 ms
Pug
3162 ms
1301 ms
adsct
1091 ms
sd
1089 ms
377928.gif
948 ms
rum
1876 ms
in
1875 ms
160 ms
in
660 ms
sync
952 ms
l
764 ms
symantec.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
symantec.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
Missing source maps for large first-party JavaScript
symantec.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
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 Symantec.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 Symantec.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.
symantec.com
Open Graph description is not detected on the main page of Symantec. 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: