3.1 sec in total
368 ms
2.5 sec
215 ms
Welcome to doc.openerp.com homepage info - get ready to check Doc Openerp best content for Vietnam right away, or after learning these important things about doc.openerp.com
Visit doc.openerp.comWe analyzed Doc.openerp.com page load time and found that the first response time was 368 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
doc.openerp.com performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value5.1 s
25/100
25%
Value6.0 s
47/100
10%
Value150 ms
95/100
30%
Value0
100/100
15%
Value6.2 s
62/100
10%
368 ms
497 ms
79 ms
157 ms
235 ms
Our browser made a total of 33 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Doc.openerp.com, 45% (15 requests) were made to Odoo.com and 24% (8 requests) were made to Doc.odoo.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Odoo.com.
Page size can be reduced by 780.3 kB (85%)
918.2 kB
137.9 kB
In fact, the total size of Doc.openerp.com main page is 918.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. 35% of websites need less resources to load. Javascripts take 632.6 kB which makes up the majority of the site volume.
Potential reduce by 24.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. This page needs HTML code to be minified as it can gain 6.0 kB, which is 20% 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 24.1 kB or 81% of the original size.
Potential reduce by 0 B
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. Doc Openerp images are well optimized though.
Potential reduce by 539.5 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 539.5 kB or 85% of the original size.
Potential reduce by 216.7 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. Doc.openerp.com needs all CSS files to be minified and compressed as it can save up to 216.7 kB or 85% of the original size.
Number of requests can be reduced by 18 (82%)
22
4
The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Doc Openerp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
doc.openerp.com
368 ms
doc.odoo.com
497 ms
normalize.css
79 ms
common.css
157 ms
website.css
235 ms
font-awesome.css
776 ms
website.css
813 ms
odoo.css
902 ms
promote_bar.css
830 ms
css
57 ms
es5-shim.min.js
831 ms
underscore.js
924 ms
underscore.string.js
851 ms
jquery.js
1153 ms
jquery.form.js
1013 ms
promote_bar.js
925 ms
openerp_enterprise_start_trial.js
926 ms
qweb2.js
981 ms
openerpframework.js
1343 ms
bootstrap.js
1251 ms
pygments.css
227 ms
patchqueue.css
227 ms
patchqueue.js
233 ms
pdf.png
115 ms
analytics.js
39 ms
1EqTbJWOZQBfhZ0e3RL9uvesZW2xOQ-xsNqO47m55DA.ttf
53 ms
0DeoTBMnW4sOpD0Zb8OQSALUuEpTyoUstqEm5AMlJo4.ttf
70 ms
MZ1aViPqjfvZwVD_tzjjkwLUuEpTyoUstqEm5AMlJo4.ttf
72 ms
jZjuDZSb58pQtWhOr6q-6ALUuEpTyoUstqEm5AMlJo4.ttf
71 ms
fontawesome-webfont.woff
268 ms
collect
23 ms
collect
58 ms
ga-audiences
68 ms
doc.openerp.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
doc.openerp.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
doc.openerp.com SEO score
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Doc.openerp.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Doc.openerp.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.
doc.openerp.com
Open Graph description is not detected on the main page of Doc Openerp. 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: