4 sec in total
479 ms
3.1 sec
342 ms
Click here to check amazing Og content for France. Otherwise, check out these important facts you probably never knew about og.cm
Discover Over-Graph! Publish, Respond and Analyze all your Profiles coming from Facebook, Twitter, etc. Strong and free-access ! Made in France
Visit og.cmWe analyzed Og.cm page load time and found that the first response time was 479 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
og.cm performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value1.3 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
479 ms
346 ms
4 ms
249 ms
166 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Og.cm, 88% (42 requests) were made to Over-graph.com and 4% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Over-graph.com.
Page size can be reduced by 679.6 kB (36%)
1.9 MB
1.2 MB
In fact, the total size of Og.cm main page is 1.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. 40% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 21.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 3.6 kB, which is 13% 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 21.3 kB or 78% of the original size.
Potential reduce by 29.3 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. Og images are well optimized though.
Potential reduce by 502.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 502.9 kB or 82% of the original size.
Potential reduce by 126.2 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. Og.cm needs all CSS files to be minified and compressed as it can save up to 126.2 kB or 85% of the original size.
Number of requests can be reduced by 3 (8%)
38
35
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Og. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
og.cm
479 ms
www.over-graph.com
346 ms
font-awesome.min.css
4 ms
style.css
249 ms
modernizr.js
166 ms
jquery.min.js
54 ms
scripts.js
579 ms
ga.js
4 ms
__utm.gif
12 ms
logo.svg
91 ms
lg.png
94 ms
slider-1.jpg
495 ms
slider-2.jpg
501 ms
slider-3.jpg
578 ms
slider-4.jpg
684 ms
slider-5.jpg
505 ms
slider-mini-1.jpg
493 ms
slider-mini-2.jpg
495 ms
slider-mini-3.jpg
537 ms
slider-mini-4.jpg
554 ms
slider-mini-5.jpg
586 ms
step-1.png
781 ms
step-2.png
924 ms
step-3.png
1151 ms
wallet.png
681 ms
home-avatar-7.png
681 ms
home-avatar-8.png
749 ms
home-avatar-9.png
750 ms
home-avatar-10.png
753 ms
home-avatar-11.png
827 ms
home-avatar-12.png
836 ms
logo-webmarketing.gif
832 ms
logo-siecle-digital-long.png
861 ms
comment_ca_marche.png
908 ms
orange-on.png
916 ms
frenchweb-on.png
917 ms
maddyness-on.png
1025 ms
logo-footer.png
990 ms
OpenSans-Regular.svg
1021 ms
OpenSans-Semibold.svg
1021 ms
OpenSans-Bold.svg
1092 ms
icons.svg
1006 ms
fontawesome-webfont.woff
15 ms
OpenSans-Italic.svg
1206 ms
OpenSans-Regular.woff
85 ms
OpenSans-Semibold.woff
188 ms
OpenSans-Bold.woff
93 ms
OpenSans-Italic.woff
87 ms
og.cm accessibility score
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
Document doesn't have a <title> element
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
og.cm best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
og.cm SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
DA
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Og.cm can be misinterpreted by Google and other search engines. Our service has detected that Danish is used on the page, and it does not match the claimed French language. Our system also found out that Og.cm 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.
og.cm
Open Graph data is detected on the main page of Og. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: