2.1 sec in total
173 ms
802 ms
1.1 sec
Click here to check amazing Forms Share content. Otherwise, check out these important facts you probably never knew about forms.share.works
Discover how we help individuals, families, institutions and governments raise, manage and distribute the capital they need to achieve their goals.
Visit forms.share.worksWe analyzed Forms.share.works page load time and found that the first response time was 173 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
forms.share.works performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value11.3 s
0/100
25%
Value9.6 s
11/100
10%
Value1,650 ms
11/100
30%
Value0
100/100
15%
Value15.7 s
6/100
10%
173 ms
56 ms
137 ms
131 ms
37 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Forms.share.works, 2% (1 request) were made to C.evidon.com and 2% (1 request) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (326 ms) relates to the external source Morganstanley.com.
Page size can be reduced by 364.3 kB (5%)
6.9 MB
6.5 MB
In fact, the total size of Forms.share.works main page is 6.9 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. Only a small number of websites need less resources to load. Images take 6.6 MB which makes up the majority of the site volume.
Potential reduce by 147.6 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 28.3 kB, which is 17% 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 147.6 kB or 89% of the original size.
Potential reduce by 216.7 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. Forms Share images are well optimized though.
Potential reduce by 12 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 7 (13%)
53
46
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Forms Share. 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 as a result speed up the page load time.
www.morganstanley.com
173 ms
dg.js
56 ms
clientlib-dependencies.min.3e24d4d067ac58228b5004abb50344ef.js
137 ms
clientlib-base.min.d62145ec3e39fdf05049a6ebd97168cf.css
131 ms
launch-82c45f0094b5.min.js
37 ms
container.min.c8339545b501e3db3abc37c9a4cc2d6e.js
72 ms
clientlib-base.min.ced8d42a04562bb81ac2a9a0f336960a.js
228 ms
site.min.c18992cc848d8ffca0c46ca5d851eaf3.css
248 ms
site.min.f902726cd997381349d0fd0963f198dc.js
213 ms
clientlib-frontend-site.min.9ccb7ccea231a567e11184db4131bc05.js
326 ms
logo-black.png
127 ms
2024-election-160x160.jpg
51 ms
fall-financial-tips-160x160.jpg
54 ms
humanoid-robots.jpg
53 ms
thumbnail-our-culture-square.jpg
51 ms
thumbnail-tech-innovator-square.jpg
118 ms
extrawide_3x1.jpg
122 ms
extrawide_3x1_hero-thoughts-on-the-market.jpg
120 ms
extrawide_3x1.jpg
124 ms
wwd_16x9.jpg
134 ms
wide_16x9.jpg
129 ms
wide_16x9.jpg
122 ms
wide_16x9.jpg
124 ms
wide_16x9.jpg
128 ms
wide_16x9.jpg
126 ms
wide_16x9.jpg
127 ms
wide_16x9.jpg
145 ms
wide_16x9.jpg
129 ms
wide_16x9.jpg
131 ms
wide_16x9.jpg
130 ms
wide_16x9.jpg
140 ms
wide_16x9.jpg
134 ms
wide_16x9.jpg
134 ms
wide_16x9.jpg
132 ms
wide_16x9.jpg
137 ms
wide_16x9.jpg
149 ms
wide_16x9.jpg
135 ms
wide_16x9.jpg
135 ms
wide_16x9.jpg
136 ms
wide_16x9.jpg
137 ms
wide_16x9.jpg
142 ms
wide_16x9.jpg
130 ms
wide_16x9.jpg
109 ms
wide_16x9.jpg
100 ms
wide_16x9.jpg
123 ms
wide_16x9.jpg
100 ms
privacyoptions29x14.jpg
98 ms
ms-icon-rt-arrow1-wt.svg
146 ms
karla-regular-webfont.woff
178 ms
ms_gloriola_ii_std_reg-webfont.woff
68 ms
karla-bold-webfont.woff
62 ms
ms_gloriola_ii_std_semibold.ttf
99 ms
fontawesome-webfont.woff
131 ms
ms-icon-linkedin-gr.svg
89 ms
ms-icon-instagram-gr.svg
95 ms
ms-icon-twitter-gr.svg
95 ms
ms-icon-facebook-gr.svg
127 ms
ms-icon-youtube-gr.svg
128 ms
ms_gloriola_ii_std_light-webfont.woff
133 ms
45 ms
forms.share.works accessibility score
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
forms.share.works 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
forms.share.works 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 Forms.share.works 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 Forms.share.works 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.
forms.share.works
Open Graph data is detected on the main page of Forms Share. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: