1.1 sec in total
111 ms
818 ms
133 ms
Visit domtar.net now to see the best up-to-date Domtar content and also check out these interesting facts you probably never knew about domtar.net
Domtar designs, manufactures, markets and distributes a wide variety of pulp, paper and personal care products.
Visit domtar.netWe analyzed Domtar.net page load time and found that the first response time was 111 ms and then it took 951 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
domtar.net performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value4.7 s
33/100
25%
Value8.0 s
22/100
10%
Value7,440 ms
0/100
30%
Value0.234
53/100
15%
Value21.9 s
1/100
10%
111 ms
29 ms
51 ms
52 ms
82 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Domtar.net, 6% (6 requests) were made to Apis.google.com and 3% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (229 ms) relates to the external source Domtar.com.
Page size can be reduced by 676.6 kB (52%)
1.3 MB
615.8 kB
In fact, the total size of Domtar.net main page is 1.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. 65% of websites need less resources to load. Javascripts take 732.7 kB which makes up the majority of the site volume.
Potential reduce by 22.7 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 22.7 kB or 74% of the original size.
Potential reduce by 8.2 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. Domtar images are well optimized though.
Potential reduce by 497.9 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 497.9 kB or 68% of the original size.
Potential reduce by 147.9 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. Domtar.net needs all CSS files to be minified and compressed as it can save up to 147.9 kB or 86% of the original size.
Number of requests can be reduced by 63 (68%)
93
30
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Domtar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.domtar.com
111 ms
DetectFlash.js
29 ms
AC_RunActiveContent.js
51 ms
Functions1.js
52 ms
styles1.css
82 ms
Survey_JQuery_132min.js
73 ms
Survey_JQuery_PrettyPhoto.js
92 ms
Survey_JS_Popup.js
47 ms
survey.css
66 ms
survey_IE6.css
69 ms
imageRotator.css
68 ms
contentflow.css
90 ms
squires-styles.css
90 ms
mycontentflow.css
92 ms
ContentFlowAddOn_white.css
93 ms
contentflow.js
107 ms
ContentFlowAddOn_Domtar.js
113 ms
ContentFlowAddOn_white.js
105 ms
in.js
26 ms
widgets.js
24 ms
platform.js
57 ms
bg_paperSelected.gif
56 ms
bg_pulpSelected.gif
63 ms
BG-Care-selected.gif
61 ms
bg_substainmabilitySelected.gif
73 ms
bg_investorsSelected.gif
74 ms
bg_corporateSelected.gif
75 ms
bg_mediaSelected.gif
75 ms
bg_paperSubMenu_over.gif
77 ms
bg_pulpSubMenu_over.gif
77 ms
BG-CareSubMenu-hover.gif
90 ms
bg_substainSubMenu_over.gif
90 ms
bg_investorsSubMenu_over.gif
92 ms
bg_corporateSubMenu_over.gif
91 ms
bg_mediaSubMenu_over.gif
92 ms
home1.jpg
98 ms
home2.jpg
108 ms
home3.jpg
110 ms
home4.jpg
110 ms
Domtar3.gif
108 ms
toggle_contactbg_off.gif
111 ms
btn_search.gif
118 ms
Giving-Back-Banner-2017_small.jpg
143 ms
Newsroom_Banner_Feb2017.jpg
157 ms
tooltip_arrow_shadow.png
118 ms
Media%20Channel%20200x75.jpg
123 ms
back_bottom.gif
96 ms
contentflow.css
85 ms
mycontentflow.css
93 ms
gtm.js
99 ms
ActivityServer.bs
22 ms
ebAttribution.js
84 ms
img_rightTopShadow.gif
54 ms
sdk.js
45 ms
secureAnonymousFramework
74 ms
11744.asp
54 ms
IR-PR.asp
185 ms
IR-WC.asp
229 ms
cb=gapi.loaded_0
55 ms
cb=gapi.loaded_1
115 ms
subscribe_embed
214 ms
toggle_contactbg.gif
52 ms
bg_homeSubMenu.gif
51 ms
bg_paper2SubMenu.gif
52 ms
bg_pulpSubMenu.gif
115 ms
bg_substainmabilitySubMenu.gif
115 ms
bg_investorsSubMenu.gif
115 ms
bg_corporateSubMenu.gif
114 ms
bg_topMenuShadow.gif
151 ms
separator2.gif
151 ms
separator.gif
151 ms
owen.png
150 ms
img_rightMiddleShadow.gif
207 ms
right_end.gif
210 ms
smedia-bkgrnd.png
207 ms
icon_press.gif
207 ms
icon_report.gif
207 ms
icon_webcast.gif
216 ms
img_rightBottomShadow.gif
216 ms
button.3ccb64e61d4c01fae12cd2b0ed9b2bab.js
98 ms
greenArrowLink_clear.gif
169 ms
209 ms
0sTQzbapM8j.js
86 ms
0sTQzbapM8j.js
119 ms
analytics.js
76 ms
postmessageRelay
128 ms
collect
29 ms
collect
77 ms
follow_button.f8c8d971a6ac545cf416e3c1ad4bbc65.en.html
27 ms
www-subscribe-embed-vfltcNtU0.css
28 ms
www-subscribe-embed.js
33 ms
www-hitchhiker-vfl-Nn88d.png
40 ms
cb=gapi.loaded_0
8 ms
971028622-postmessagerelay.js
27 ms
rpc:shindig_random.js
31 ms
cb=gapi.loaded_0
5 ms
domtar.net 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
domtar.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
domtar.net SEO score
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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Domtar.net 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 Domtar.net 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.
domtar.net
Open Graph description is not detected on the main page of Domtar. 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: