3.4 sec in total
324 ms
3 sec
110 ms
Visit demo2.openerp.com now to see the best up-to-date Demo 2 Openerp content for Vietnam and also check out these interesting facts you probably never knew about demo2.openerp.com
Visit demo2.openerp.comWe analyzed Demo2.openerp.com page load time and found that the first response time was 324 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
demo2.openerp.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value5.6 s
18/100
25%
Value7.1 s
31/100
10%
Value1,390 ms
16/100
30%
Value0.214
58/100
15%
Value12.1 s
16/100
10%
324 ms
87 ms
1204 ms
50 ms
58 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Demo2.openerp.com, 50% (26 requests) were made to Odoocdn.com and 35% (18 requests) were made to Odoo.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Odoo.com.
Page size can be reduced by 1.9 MB (74%)
2.6 MB
666.6 kB
In fact, the total size of Demo2.openerp.com main page is 2.6 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. 70% of websites need less resources to load. Javascripts take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 16.3 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 7.8 kB, which is 40% 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 16.3 kB or 83% of the original size.
Potential reduce by 10.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. Demo 2 Openerp images are well optimized though.
Potential reduce by 1.5 MB
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.5 MB or 75% of the original size.
Potential reduce by 366.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. Demo2.openerp.com needs all CSS files to be minified and compressed as it can save up to 366.9 kB or 85% of the original size.
Number of requests can be reduced by 7 (32%)
22
15
The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Demo 2 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 8 to 1 for JavaScripts and as a result speed up the page load time.
demo2.openerp.com
324 ms
demo2.openerp.com
87 ms
typo
1204 ms
web.assets_common.0.css
50 ms
website.assets_frontend.0.css
58 ms
website.assets_frontend.1.css
70 ms
web.assets_common.js
88 ms
website.assets_frontend.js
82 ms
createjs-2013.12.12.min.js
406 ms
movieclip-0.6.0.min.js
389 ms
websiteBuilder.js
396 ms
logo_inverse_white_206px.png
8 ms
i.js
16 ms
3459dcaebabf1b28665d3c910bc5d6e13ac6f7ed.2.js
99 ms
fontawesome-webfont.woff
8 ms
Lato-Italic.ttf
612 ms
Lato-RegIta-webfont.woff
433 ms
Lato-LightItalic.ttf
512 ms
Lato-LigIta-webfont.woff
365 ms
Lato-HaiIta-webfont.woff
448 ms
Lato-BoldItalic.ttf
616 ms
Lato-BolIta-webfont.woff
800 ms
Lato-BlaIta-webfont.woff
798 ms
Lato-Regular.ttf
453 ms
Lato-Reg-webfont.woff
460 ms
Lato-Light.ttf
475 ms
Lato-Lig-webfont.woff
481 ms
Lato-Hai-webfont.woff
485 ms
Lato-Bold.ttf
490 ms
Lato-Bol-webfont.woff
495 ms
Lato-Bla-webfont.woff
501 ms
analytics.js
66 ms
website.xml
88 ms
banner.jpg
137 ms
collect
11 ms
base_common.xml
173 ms
collect
60 ms
ga-audiences
29 ms
footer.jpg
100 ms
website.share.xml
90 ms
header_1.jpg
86 ms
website_blog.inline.discussion.xml
89 ms
header_2.jpg
84 ms
website_forum_share_templates.xml
92 ms
header_snippets.jpg
85 ms
chatter_message.xml
89 ms
ico_creation.png
159 ms
rating_common.xml
88 ms
main_first.jpg
81 ms
website.twitter.xml
87 ms
message.jpg
81 ms
mouse_default.png
80 ms
demo2.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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
demo2.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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
demo2.openerp.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Demo2.openerp.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 Demo2.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.
demo2.openerp.com
Open Graph description is not detected on the main page of Demo 2 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: