3.5 sec in total
718 ms
2.2 sec
605 ms
Click here to check amazing Odimin content for India. Otherwise, check out these important facts you probably never knew about odimin.com
A Mining Engineer's Blog
Visit odimin.comWe analyzed Odimin.com page load time and found that the first response time was 718 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.
odimin.com performance score
name
value
score
weighting
Value2.7 s
60/100
10%
Value2.7 s
86/100
25%
Value2.7 s
96/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.7 s
97/100
10%
718 ms
14 ms
88 ms
115 ms
94 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Odimin.com, 17% (16 requests) were made to Fbstatic-a.akamaihd.net and 8% (8 requests) were made to S2.wp.com. The less responsive or slowest element that took the longest time to load (718 ms) belongs to the original domain Odimin.com.
Page size can be reduced by 503.9 kB (72%)
695.9 kB
192.0 kB
In fact, the total size of Odimin.com main page is 695.9 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. 80% 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 531.6 kB which makes up the majority of the site volume.
Potential reduce by 79.5 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 79.5 kB or 78% of the original size.
Potential reduce by 515 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. Odimin images are well optimized though.
Potential reduce by 384.7 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 384.7 kB or 72% of the original size.
Potential reduce by 39.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. Odimin.com needs all CSS files to be minified and compressed as it can save up to 39.2 kB or 79% of the original size.
Number of requests can be reduced by 49 (59%)
83
34
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Odimin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
odimin.com
718 ms
webfont.js
14 ms
88 ms
css
115 ms
94 ms
84 ms
93 ms
style.css
97 ms
gprofiles.js
159 ms
wpgroho.js
89 ms
80 ms
94 ms
tiled-gallery.css
92 ms
94 ms
widgets.js
237 ms
86 ms
725X1342.skimlinks.js
93 ms
w.js
75 ms
merriweather.css
28 ms
cropped-hands-support-min.jpg
105 ms
sdk.js
96 ms
b495a0c3cb8332fd60d42f1004c3e58c
209 ms
survey.js
208 ms
widgets.js
108 ms
appicon-512x512_558fae08e9ea0.jpg
256 ms
8d797646086c4bb08f797162972dab0a
193 ms
a96414de43f47c10f24fb886cd1b8e39
313 ms
7fd9e2ee486de5ce0c713891ec823ea6
385 ms
fVu1p3782bqS2z-CaJvp9i3USBnSvpkopQaUR-2r7iU.ttf
312 ms
lJAvZoKA5NttpPc9yc6lPbOLyRJkM5aLlPlkJMOAyH0.ttf
347 ms
cropped-hands-support-min.jpg
261 ms
PIbvSEyHEdL91QLOQRnZ19qQynqKV_9Plp7mupa0S4g.ttf
260 ms
erE3KsIWUumgD1j_Ca-V-6CWcynf_cDxXwCLxiixG1c.ttf
267 ms
Genericons.svg
169 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
20 ms
HQXBIwLHsOJCNEQeX9kNz9qQynqKV_9Plp7mupa0S4g.ttf
266 ms
Wreg0Be4tcFGM2t6VWytvKp5NA6AAOjfQM_HmvD0shQ.ttf
267 ms
Noticons.svg
167 ms
BaABdRAi2AAAA
19 ms
merriweather-bold-webfont.ttf
166 ms
merriweather-regular-webfont.ttf
222 ms
merriweather-light-webfont.ttf
257 ms
172 ms
hovercard.css
151 ms
services.css
176 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
249 ms
154 ms
295 ms
g.gif
146 ms
g.gif
147 ms
g.gif
147 ms
xd_arbiter.php
147 ms
xd_arbiter.php
179 ms
page.php
339 ms
syndication
105 ms
627488506504310784
170 ms
banner
391 ms
link
16 ms
track.php
19 ms
proxy.jpg
37 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
28 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
57 ms
ym6Qu6-m_normal.png
256 ms
i6Z2J-8b_normal.jpg
262 ms
CaG_MrOXEAAh1Kf.jpg:small
379 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
50 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
57 ms
Ezryo55Cca5.css
59 ms
HKna9a9CcB_.css
68 ms
m3UplzJmRpp.css
69 ms
q68gy-v_YMF.js
73 ms
YvxwM8R7ol8.js
92 ms
ihptErjAmMX.js
98 ms
3So47A9WcrL.js
98 ms
cUsKAwzqrQw.js
101 ms
proxy.jpg
5 ms
11796212_1166458010037465_3818425557035673721_n.jpg
84 ms
safe_image.php
238 ms
lRyN50VcaFW.js
16 ms
safe_image.php
346 ms
safe_image.php
269 ms
11220927_1166083723408227_8281031121002201123_n.jpg
55 ms
10610901_958632160924670_9001886030192836376_n.jpg
56 ms
10271620_236403003371900_913661015333359578_n.jpg
57 ms
10299073_157764861269793_84196950823113756_n.jpg
57 ms
10354686_10150004552801856_220367501106153455_n.jpg
56 ms
12651374_1649612031944484_6964245501783230865_n.jpg
57 ms
wL6VQj7Ab77.png
14 ms
s7jcwEQH7Sx.png
14 ms
GtIpNnEyqq_.png
14 ms
jot.html
29 ms
jot
26 ms
R9a_DtVRZgv.js
71 ms
cUDgRFxaoIk.js
71 ms
0JBr1QHp8Gi.js
71 ms
kDOzhTr2W91.js
72 ms
odimin.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.
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
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
Form elements do not have associated labels
odimin.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
odimin.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Odimin.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 Odimin.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.
odimin.com
Open Graph data is detected on the main page of Odimin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: