5.2 sec in total
251 ms
4.1 sec
904 ms
Click here to check amazing S Docs content for United States. Otherwise, check out these important facts you probably never knew about sdocs.com
S-Docs is the only 100% Native Salesforce Document Generation & E-Signature tool. Guaranteed speed & data security. Easily installed through the AppExchange.
Visit sdocs.comWe analyzed Sdocs.com page load time and found that the first response time was 251 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
sdocs.com performance score
name
value
score
weighting
Value8.4 s
0/100
10%
Value28.7 s
0/100
25%
Value43.8 s
0/100
10%
Value56,770 ms
0/100
30%
Value0.134
80/100
15%
Value82.5 s
0/100
10%
251 ms
350 ms
152 ms
143 ms
328 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 73% of them (113 requests) were addressed to the original Sdocs.com, 6% (9 requests) were made to Fonts.gstatic.com and 3% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Sdocs.com.
Page size can be reduced by 295.2 kB (31%)
956.2 kB
661.1 kB
In fact, the total size of Sdocs.com main page is 956.2 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. 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 629.3 kB which makes up the majority of the site volume.
Potential reduce by 204.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. 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 204.8 kB or 83% of the original size.
Potential reduce by 90.0 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, S Docs needs image optimization as it can save up to 90.0 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 279 B
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.
Number of requests can be reduced by 109 (81%)
135
26
The browser has sent 135 CSS, Javascripts, AJAX and image requests in order to completely render the main page of S Docs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 88 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
sdocs.com
251 ms
www.sdocs.com
350 ms
gtm.js
152 ms
wp-emoji-release.min.js
143 ms
style.min.css
328 ms
widgets.css
128 ms
rgs.css
129 ms
font-awesome.min.css
360 ms
style.css
191 ms
mediaelementplayer-legacy.min.css
318 ms
wp-mediaelement.min.css
315 ms
style.css
316 ms
magnific.css
335 ms
responsive.css
366 ms
dynamic-combined.css
341 ms
ascend.css
338 ms
js_composer.min.css
376 ms
enlighterjs.min.css
396 ms
bellows.min.css
402 ms
colors.css
405 ms
main.min.css
424 ms
font-awesome.min.css
412 ms
main.min.css
446 ms
jquery.min.js
125 ms
modernizr.js
408 ms
css
135 ms
v2.js
167 ms
shCore.js
419 ms
shBrushAS3.js
430 ms
shBrushArduino.js
745 ms
shBrushBash.js
747 ms
shBrushColdFusion.js
749 ms
shBrushClojure.js
741 ms
shBrushCpp.js
738 ms
shBrushCSharp.js
740 ms
shBrushCss.js
742 ms
shBrushDelphi.js
742 ms
shBrushDiff.js
745 ms
shBrushErlang.js
744 ms
shBrushFSharp.js
742 ms
shBrushGo.js
746 ms
animate.min.css
739 ms
shBrushGroovy.js
639 ms
shBrushHaskell.js
639 ms
shBrushJava.js
767 ms
shBrushJavaFX.js
600 ms
shBrushJScript.js
598 ms
shBrushLatex.js
594 ms
shBrushMatlabKey.js
584 ms
shBrushObjC.js
577 ms
shBrushPerl.js
647 ms
shBrushPhp.js
644 ms
shBrushPlain.js
624 ms
shBrushPowerShell.js
622 ms
shBrushPython.js
589 ms
shBrushR.js
584 ms
shBrushRuby.js
694 ms
shBrushScala.js
701 ms
shBrushSql.js
687 ms
shBrushSwift.js
686 ms
shBrushVb.js
681 ms
shBrushXml.js
674 ms
shBrushYaml.js
903 ms
core.min.js
896 ms
bumts3aep34m.js
372 ms
hotjar-1894559.js
424 ms
stars
696 ms
5238529.js
474 ms
api.js
583 ms
insight.min.js
888 ms
js
330 ms
5104.js
548 ms
menu.min.js
580 ms
regenerator-runtime.min.js
581 ms
wp-polyfill.min.js
578 ms
dom-ready.min.js
579 ms
hooks.min.js
843 ms
i18n.min.js
843 ms
a11y.min.js
841 ms
autocomplete.min.js
840 ms
wpss-search-suggest.js
841 ms
magnific.js
839 ms
touchswipe.min.js
1094 ms
caroufredsel.min.js
1005 ms
owl.carousel.min.js
1092 ms
superfish.js
1002 ms
init.js
1089 ms
KFOmCnqEu92Fr1Mu4mxM.woff
344 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
552 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
552 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
551 ms
infinitescroll.js
969 ms
json
645 ms
mediaelement-and-player.min.js
960 ms
mediaelement-migrate.min.js
959 ms
wp-mediaelement.min.js
958 ms
flickity.min.js
1124 ms
jquery.flexslider-min.js
1124 ms
stickkit.js
1052 ms
enlighterjs.min.js
1051 ms
detectmobilebrowser.js
1052 ms
theia-sticky-sidebar.js
1049 ms
bellows.min.js
1132 ms
wp-embed.min.js
1126 ms
js_composer_front.min.js
1140 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTQ3iQ.woff
342 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTQ3iQ.woff
342 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3iQ.woff
340 ms
KFOjCnqEu92Fr1Mu51TjASc6CsI.woff
613 ms
KFOkCnqEu92Fr1Mu51xIIzQ.woff
612 ms
modules.61e17720cf639c3e96a7.js
594 ms
sdocs_logo.svg
1022 ms
sdocs_logo_inverse.svg
1016 ms
sdocs_logo.svg
1018 ms
video.jpg
1150 ms
fontawesome-webfont.woff
1150 ms
fontawesome-webfont.svg
1143 ms
fb.js
551 ms
leadflows.js
638 ms
5238529.js
632 ms
5238529.js
631 ms
recaptcha__en.js
627 ms
analytics.js
545 ms
js
430 ms
icomoon.woff
919 ms
OpenSans-Regular-webfont.woff
916 ms
OpenSans-Light-webfont.woff
862 ms
OpenSans-Semibold-webfont.woff
971 ms
OpenSansBold-webfont.woff
1026 ms
S-Docs-G2-Badges-Winter-2022.png
1100 ms
json
222 ms
shCore.css
706 ms
shThemeDefault.css
704 ms
logo_unilever.png
762 ms
logo_johnsonjohnson.png
848 ms
logo_roche.png
851 ms
logo_unitedhealthcare.png
849 ms
logo_intel.png
682 ms
logo_va.png
686 ms
conversion_async.js
253 ms
loader.js
65 ms
logo_philips.png
598 ms
logo_nestle.png
599 ms
S-Docs-Home-Screen.jpg
605 ms
www.sdocs.com
594 ms
collect
28 ms
call-tracking_7.js
13 ms
collect
80 ms
119 ms
wcm
37 ms
ga-audiences
24 ms
66 ms
73 ms
fontawesome-webfont.woff
846 ms
sdocs.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
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
sdocs.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
Missing source maps for large first-party JavaScript
sdocs.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sdocs.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 Sdocs.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.
sdocs.com
Open Graph data is detected on the main page of S Docs. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: