Tools & Wizards About Us
docscience.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

docscience.com

Enterprise Content Management | OpenText Documentum Platform

Page Load Speed

1.7 sec in total

First Response

144 ms

Resources Loaded

1.5 sec

Page Rendered

127 ms

docscience.com screenshot

About Website

Click here to check amazing Docscience content. Otherwise, check out these important facts you probably never knew about docscience.com

Get the foundation for enterprise content management and intelligent case management with OpenText Documentum.

Visit docscience.com

Key Findings

We analyzed Docscience.com page load time and found that the first response time was 144 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

docscience.com performance score

0

Network Requests Diagram

docscience.com

144 ms

index.htm

241 ms

html-layout-css-includes-combined-min.css

16 ms

html-layout-js-header-includes-combined.js

26 ms

scriptaculous.js

64 ms

Our browser made a total of 117 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Docscience.com, 51% (60 requests) were made to Emc.com and 9% (10 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (241 ms) relates to the external source Emc.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.5 MB (64%)

Content Size

3.9 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Docscience.com main page is 3.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. 75% 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. Javascripts take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 64.9 kB

  • Original 85.1 kB
  • After minification 79.5 kB
  • After compression 20.2 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 64.9 kB or 76% of the original size.

Image Optimization

-8%

Potential reduce by 22.9 kB

  • Original 290.7 kB
  • After minification 267.8 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. Docscience images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 1.9 MB

  • Original 2.6 MB
  • After minification 2.4 MB
  • After compression 716.6 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 1.9 MB or 73% of the original size.

CSS Optimization

-54%

Potential reduce by 478.5 kB

  • Original 881.1 kB
  • After minification 776.0 kB
  • After compression 402.6 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. Docscience.com needs all CSS files to be minified and compressed as it can save up to 478.5 kB or 54% of the original size.

Requests Breakdown

Number of requests can be reduced by 92 (83%)

Requests Now

111

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Docscience. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 52 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

docscience.com

docscience.com

144 ms

index.htm

index.htm

241 ms

html-layout-css-includes-combined-min.css

html-layout-css-includes-combined-min.css

16 ms

html-layout-js-header-includes-combined.js

html-layout-js-header-includes-combined.js

26 ms

scriptaculous.js

scriptaculous.js

64 ms

header.css

header.css

45 ms

jquery.js

jquery.js

37 ms

header.js

header.js

38 ms

satelliteLib-c3c3c7ad9967d3bb40540600d09c43ef34628abc.js

satelliteLib-c3c3c7ad9967d3bb40540600d09c43ef34628abc.js

39 ms

utilityBar.js

utilityBar.js

37 ms

utilityBar.css

utilityBar.css

117 ms

support.css

support.css

37 ms

freeform.css

freeform.css

37 ms

integration.css

integration.css

35 ms

productfamily.css

productfamily.css

118 ms

integration.css

integration.css

38 ms

breadcrumb.css

breadcrumb.css

41 ms

landing-reskin-nov2011.css

landing-reskin-nov2011.css

46 ms

corporate.css

corporate.css

42 ms

cufon-yui.js

cufon-yui.js

45 ms

meta.js

meta.js

48 ms

ext-all.js

ext-all.js

110 ms

cufon-yui.js

cufon-yui.js

55 ms

MetaMedium.font.js

MetaMedium.font.js

108 ms

cufonReplace.js

cufonReplace.js

110 ms

modal.js

modal.js

110 ms

tableStyler.js

tableStyler.js

109 ms

jquery.history.js

jquery.history.js

109 ms

landing-reskin-nov2011.js

landing-reskin-nov2011.js

233 ms

os-142-0.js

os-142-0.js

108 ms

header.js

header.js

110 ms

modal.css

modal.css

123 ms

s_code.js

s_code.js

109 ms

BrightcoveExperiences.js

BrightcoveExperiences.js

36 ms

APIModules_all.js

APIModules_all.js

38 ms

input-typeahead.js

input-typeahead.js

34 ms

mbox-contents-25e762a9c1c1cad8fe89059fd3d61922d99f6221.js

mbox-contents-25e762a9c1c1cad8fe89059fd3d61922d99f6221.js

12 ms

oct.js

oct.js

53 ms

satellite-52f278378f0de5bc9400054f.js

satellite-52f278378f0de5bc9400054f.js

10 ms

satellite-548b064a3436330015340200.js

satellite-548b064a3436330015340200.js

10 ms

satellite-5575d7c23966620014220500.js

satellite-5575d7c23966620014220500.js

12 ms

satellite-5553bf0d6335611a583e0700.js

satellite-5553bf0d6335611a583e0700.js

10 ms

satellite-54eb6f4537376451110c0400.js

satellite-54eb6f4537376451110c0400.js

11 ms

satellite-52f5622461eb66e904000316.js

satellite-52f5622461eb66e904000316.js

10 ms

satellite-52f56127e6129c4f530001be.js

satellite-52f56127e6129c4f530001be.js

12 ms

satellite-52f55e3de6129c4f530001bb.js

satellite-52f55e3de6129c4f530001bb.js

10 ms

header-sprites-dec14.png

header-sprites-dec14.png

40 ms

header-menu-sprites-dec14.png

header-menu-sprites-dec14.png

25 ms

EMC_Image_C_1310663844078_domain-page-banner-docsci-LAYOUT-REFERENCE.png

EMC_Image_C_1310663844078_domain-page-banner-docsci-LAYOUT-REFERENCE.png

92 ms

EMC_Image_C_1310586481662_fbook_icon.png

EMC_Image_C_1310586481662_fbook_icon.png

128 ms

EMC_Image_C_1310586483248_twit_icon.png

EMC_Image_C_1310586483248_twit_icon.png

30 ms

EMC_Image_C_1310586484068_linkedin_icon.png

EMC_Image_C_1310586484068_linkedin_icon.png

27 ms

EMC_Image_C_1310592538131_icon-youtube.jpg

EMC_Image_C_1310592538131_icon-youtube.jpg

94 ms

EMC_Image_C_1310592538393_icon-rss.jpg

EMC_Image_C_1310592538393_icon-rss.jpg

222 ms

adsct

adsct

103 ms

adsct

adsct

39 ms

ip.js

ip.js

17 ms

target.js

target.js

27 ms

standard

standard

32 ms

rd

rd

6 ms

id

id

51 ms

standard

standard

8 ms

gtm.js

gtm.js

31 ms

layout.css

layout.css

49 ms

globalNav.css

globalNav.css

6 ms

secondaryNav.css

secondaryNav.css

16 ms

footer.css

footer.css

87 ms

localization.css

localization.css

11 ms

buttons.css

buttons.css

7 ms

globalsiteselector.css

globalsiteselector.css

9 ms

freeform.css

freeform.css

12 ms

box.css

box.css

13 ms

buttons.css

buttons.css

45 ms

breadcrumb.css

breadcrumb.css

15 ms

leadspace.css

leadspace.css

46 ms

dynamicContentStyles.css

dynamicContentStyles.css

45 ms

contentList.css

contentList.css

95 ms

productfamily.css

productfamily.css

179 ms

analytics.js

analytics.js

9 ms

insight.min.js

insight.min.js

22 ms

rvzEBznY.min.js

rvzEBznY.min.js

25 ms

linkid.js

linkid.js

9 ms

adsct

adsct

37 ms

adsct

adsct

39 ms

collect

collect

9 ms

collect

collect

63 ms

ect.html

ect.html

30 ms

pixel

pixel

21 ms

pixel

pixel

8 ms

ip.json

ip.json

7 ms

ga-audiences

ga-audiences

143 ms

landing-sprites.png

landing-sprites.png

101 ms

EMC_Image_C_1310586489569_vdiv.jpg

EMC_Image_C_1310586489569_vdiv.jpg

99 ms

menudropdown.inc

menudropdown.inc

102 ms

os-ue-lib-1.1.2.js

os-ue-lib-1.1.2.js

93 ms

userInfo.htm

userInfo.htm

153 ms

collect

collect

55 ms

ip.js

ip.js

47 ms

liveperson-country-and-page-list.js

liveperson-country-and-page-list.js

151 ms

collect

collect

31 ms

46 ms

ajax

ajax

32 ms

s76021678217221

s76021678217221

27 ms

event

event

25 ms

collect

collect

25 ms

dropdown-menu-sprites-dec14.png

dropdown-menu-sprites-dec14.png

112 ms

g15gUDpvi3xw9hev5f08EnXngFjg==

g15gUDpvi3xw9hev5f08EnXngFjg==

4 ms

azr4BNtEBKY=

azr4BNtEBKY=

3 ms

bounce

bounce

11 ms

bounce

bounce

26 ms

bounce

bounce

25 ms

23 ms

deploy2.asp

deploy2.asp

137 ms

12 ms

mTag.js

mTag.js

24 ms

l

l

43 ms

50 ms

SEO Factors

docscience.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Docscience.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Docscience.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.

Social Sharing Optimization

docscience.com

Open Graph description is not detected on the main page of Docscience. 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: