3.9 sec in total
701 ms
2.9 sec
280 ms
Click here to check amazing Share content for India. Otherwise, check out these important facts you probably never knew about share.com
The Share Centre is now part of interactive investor. Find out more about your new service and about how to set up your account.
Visit share.comWe analyzed Share.com page load time and found that the first response time was 701 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
share.com performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value9.9 s
0/100
25%
Value7.1 s
31/100
10%
Value3,160 ms
2/100
30%
Value0
100/100
15%
Value13.8 s
10/100
10%
701 ms
356 ms
810 ms
36 ms
160 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 67% of them (45 requests) were addressed to the original Share.com, 4% (3 requests) were made to Stats.g.doubleclick.net and 3% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Share.com.
Page size can be reduced by 203.5 kB (34%)
590.4 kB
386.9 kB
In fact, the total size of Share.com main page is 590.4 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. 30% of websites need less resources to load. Images take 257.7 kB which makes up the majority of the site volume.
Potential reduce by 70.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 70.1 kB or 76% of the original size.
Potential reduce by 26.6 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. Share images are well optimized though.
Potential reduce by 104.0 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 104.0 kB or 44% of the original size.
Potential reduce by 2.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. Share.com needs all CSS files to be minified and compressed as it can save up to 2.8 kB or 72% of the original size.
Number of requests can be reduced by 32 (51%)
63
31
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 14 to 1 for JavaScripts and as a result speed up the page load time.
www.share.com
701 ms
css
356 ms
scripts
810 ms
tp.widget.sync.bootstrap.min.js
36 ms
3945168750.js
160 ms
ebOneTag.js
40 ms
WebResource.axd
237 ms
WebResource.axd
306 ms
validators.js
305 ms
conversion.js
49 ms
dc.js
174 ms
analytics.js
118 ms
gtm.js
174 ms
tp.widget.bootstrap.min.js
33 ms
event
142 ms
bg-content.gif
293 ms
the-share-centre-simply-easier.png
189 ms
chart_image
760 ms
acorn-green.png
290 ms
coffee_green.png
294 ms
balloon-green.png
285 ms
line-chart-green.png
292 ms
ajaxloader.gif
321 ms
advfn-internalpromo.jpg
468 ms
shares-2015.png
484 ms
invest-trends-2015-cs2.png
390 ms
shares-ISA-provider-2014.png
472 ms
Personal_finance.png
381 ms
ADVFN-Best-online.png
507 ms
OPWA_best_stock.png
471 ms
mobile.png
479 ms
sprite-icons-footer.png
558 ms
bg-header.gif
559 ms
cookie-warning.png
561 ms
bg-pipe.png
563 ms
bg-pipe-dots.png
572 ms
bg-dot-vertical-grey.png
594 ms
button-search.png
639 ms
sprite-arrows.png
643 ms
sprite-bg-tab.png
646 ms
Serving
142 ms
supporters-central-carousel.jpg
840 ms
dots-h-colour1.png
630 ms
dots-h-grey-transparent.png
664 ms
win2016.jpg
757 ms
sprite-icons-links-large.png
666 ms
bg-columns-dots.png
667 ms
sprite-icons-links.png
690 ms
bg-internal-promo.png
754 ms
dots-h-grey.png
752 ms
icon-warning.png
756 ms
bg-footer-top.gif
784 ms
bg-columns.png
1005 ms
bg-columns-horizontal.png
1009 ms
92 ms
collect
42 ms
collect
38 ms
fbevents.js
286 ms
__utm.gif
28 ms
ga-audiences
71 ms
94 ms
quant.js
46 ms
pixel;r=1106727300;a=p-NxWBXSMpVBbhR;labels=_fp.event.Homepage;fpan=1;fpa=P0-1923508583-1456753555697;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456753555697;tzo=-180;ref=;url=https%3A%2F%2Fwww.share.com%2F;ogl=
26 ms
bg-columns-sublinks.png
800 ms
Index
793 ms
106 ms
print.css
94 ms
share.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
share.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
Page has valid source maps
share.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
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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Share.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 Share.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
share.com
Open Graph description is not detected on the main page of Share. 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: