7.5 sec in total
741 ms
6.2 sec
568 ms
Click here to check amazing Omex content. Otherwise, check out these important facts you probably never knew about omex.co.in
Chawla Fire Protection Engineers Pvt. Ltd. are the leading Manufacturer and Supplier of Fire Fighting Equipment,Fire Protection Extinguishers,Fire Alarm System Suppliers India.
Visit omex.co.inWe analyzed Omex.co.in page load time and found that the first response time was 741 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
omex.co.in performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value21.4 s
0/100
25%
Value16.0 s
0/100
10%
Value240 ms
86/100
30%
Value0.378
28/100
15%
Value18.6 s
3/100
10%
741 ms
1029 ms
74 ms
62 ms
246 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 79% of them (63 requests) were addressed to the original Omex.co.in, 9% (7 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Omex.co.in.
Page size can be reduced by 92.3 kB (4%)
2.1 MB
2.0 MB
In fact, the total size of Omex.co.in main page is 2.1 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. 30% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 54.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 15.1 kB, which is 24% 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 54.1 kB or 87% of the original size.
Potential reduce by 25.4 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. Omex images are well optimized though.
Potential reduce by 9.0 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. This website has mostly compressed JavaScripts.
Potential reduce by 3.8 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. Omex.co.in needs all CSS files to be minified and compressed as it can save up to 3.8 kB or 12% of the original size.
Number of requests can be reduced by 12 (17%)
70
58
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Omex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
omex.co.in
741 ms
www.omex.co.in
1029 ms
bootstrap.min.css
74 ms
css
62 ms
conditional.css
246 ms
fluid_dg.css
486 ms
magiczoomplus.css
681 ms
element.js
86 ms
getSeal
249 ms
30d3c2bc83.js
95 ms
jquery-1.10.2.min.js
59 ms
popper.min.js
68 ms
bootstrap.min.js
82 ms
script.int.dg.js
731 ms
trustlogo.js
133 ms
whatsaap.png
229 ms
top-bg.jpg
342 ms
logo.png
346 ms
download-brochure.png
277 ms
thumb_150_67_clie-6yPqq.jpg
455 ms
thumb_150_67_abLr1n.jpg
515 ms
thumb_150_67_indexeTsx.jpg
588 ms
thumb_150_67_index6oZ0.jpg
593 ms
thumb_150_67_indexVSEY.jpg
681 ms
thumb_150_67_indexgnwz.jpg
709 ms
thumb_150_67_imagesxhIn.jpg
739 ms
thumb_150_67_index8oFh.jpg
752 ms
thumb_150_67_indexSuVr.jpg
834 ms
thumb_150_67_index0aQx.jpg
838 ms
thumb_150_67_images91vU.jpg
907 ms
thumb_150_67_mc_dmcGJ.jpg
946 ms
thumb_150_67_imagesZjeO.jpg
986 ms
thumb_150_67_1PQZ9.jpg
990 ms
thumb_150_67_Image_18yVG.jpg
1080 ms
thumb_150_67_indexA7tY.jpg
1083 ms
thumb_150_67_indexauvf.jpg
1133 ms
thumb_150_67_indexP7YM.jpg
1181 ms
thumb_150_67_imagesbaws.jpg
1232 ms
thumb_150_67_imagesQ1PT.jpg
1228 ms
thumb_285_261_IMG_4592bOD5.jpg
1327 ms
thumb_285_261_IMG_2005T47B.jpg
1329 ms
thumb_285_261_IMG_45980N8j.jpg
1359 ms
thumb_285_261_IMG_6931UUXM.jpg
1418 ms
thumb_285_261_3_Way_with_CapXmXF.jpg
1465 ms
thumb_285_261_IMG_68431fay.jpg
1478 ms
thumb_285_261_4_WayoX36.jpg
1574 ms
why.png
3050 ms
view.jpg
1585 ms
thumb_285_261_images_(1)NYen.jpg
1654 ms
thumb_285_261_images6aO4.jpg
1689 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
48 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
48 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
63 ms
pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf
69 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
68 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
70 ms
pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf
70 ms
thumb_285_261_DIY-pipe-shotgun-slam-fire-Pop-A-410-kit-gun-build-survival-weapon-6VqUQ.jpg
1679 ms
siteseal_sf_3_h_l_m.gif
69 ms
helpers.min.js
1845 ms
typeahead.js
1540 ms
fluid_dg.min.js
1554 ms
thumb_285_261_Guide_To_Fire_Extinguishers_600JfCG.jpg
1599 ms
thumb_285_261_gal-4z5Qe.jpg
1520 ms
thumb_285_261_gal-3dp0Y.jpg
1528 ms
thumb_285_261_gal-2Zv5S.jpg
1545 ms
thumb_285_261_gal-1iHej.jpg
1591 ms
map.png
1540 ms
weblink.png
1561 ms
pro-cate.jpg
2323 ms
wel.jpg
1616 ms
why-choose-us.jpg
2303 ms
counter.jpg
2124 ms
wels.jpg
1589 ms
submit.png
1659 ms
top.png
1738 ms
fl-1.png
239 ms
fl-2.png
228 ms
fluid_dg_skins.png
249 ms
omex_3WKKE.jpg
495 ms
omex.co.in 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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
omex.co.in 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
Page has valid source maps
omex.co.in SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Omex.co.in can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Omex.co.in 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.
omex.co.in
Open Graph description is not detected on the main page of Omex. 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: