Tools & Wizards About Us
intimar.in screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    72% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

intimar.in

Smart Facility Management Services | Intimar | India

Page Load Speed

1 sec in total

First Response

68 ms

Resources Loaded

779 ms

Page Rendered

182 ms

intimar.in screenshot

About Website

Visit intimar.in now to see the best up-to-date Intimar content and also check out these interesting facts you probably never knew about intimar.in

Intimar Services is one of the Top Integrated Smart Facility Management Companies in India. Visit Website to Learn More.

Visit intimar.in

Key Findings

We analyzed Intimar.in page load time and found that the first response time was 68 ms and then it took 961 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

intimar.in performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

www.intimar.in

68 ms

minified.js

52 ms

focus-within-polyfill.js

49 ms

polyfill.min.js

228 ms

thunderbolt-commons.1e70fbb2.bundle.min.js

81 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Intimar.in, 51% (19 requests) were made to Static.wixstatic.com and 41% (15 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (228 ms) relates to the external source Polyfill.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 487.1 kB (48%)

Content Size

1.0 MB

After Optimization

533.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Intimar.in main page is 1.0 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. 50% of websites need less resources to load. HTML takes 533.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 416.9 kB

  • Original 533.6 kB
  • After minification 531.5 kB
  • After compression 116.7 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 416.9 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 11.0 kB

  • Original 210.2 kB
  • After minification 199.2 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. Intimar images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 59.3 kB

  • Original 276.8 kB
  • After minification 276.8 kB
  • After compression 217.6 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 59.3 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (33%)

Requests Now

30

After Optimization

20

  • Images
  • JavaScript

The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Intimar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

www.intimar.in

www.intimar.in

68 ms

minified.js

minified.js

52 ms

focus-within-polyfill.js

focus-within-polyfill.js

49 ms

polyfill.min.js

polyfill.min.js

228 ms

thunderbolt-commons.1e70fbb2.bundle.min.js

thunderbolt-commons.1e70fbb2.bundle.min.js

81 ms

main.42e492e1.bundle.min.js

main.42e492e1.bundle.min.js

82 ms

lodash.min.js

lodash.min.js

82 ms

react.production.min.js

react.production.min.js

80 ms

react-dom.production.min.js

react-dom.production.min.js

82 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

82 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

81 ms

Intimar%20logo.png

Intimar%20logo.png

164 ms

Intimar%20logo%20white.png

Intimar%20logo%20white.png

178 ms

Intimar%20App.png

Intimar%20App.png

207 ms

0cdb49_2400c5e6881a4dd0bd4eeb7f5f721327~mv2.jpg

0cdb49_2400c5e6881a4dd0bd4eeb7f5f721327~mv2.jpg

175 ms

0cdb49_df146c57c76f41d39882f4f6be5f4fa7~mv2.jpg

0cdb49_df146c57c76f41d39882f4f6be5f4fa7~mv2.jpg

177 ms

0cdb49_972a7b3427e64a3eb0f199314efe4c9e~mv2.jpg

0cdb49_972a7b3427e64a3eb0f199314efe4c9e~mv2.jpg

176 ms

087452_9831b14ce76a496cab3f193801cf16bd~mv2.jpg

087452_9831b14ce76a496cab3f193801cf16bd~mv2.jpg

175 ms

0cdb49_c91c93f82f694ee998bee72999870aab~mv2.jpg

0cdb49_c91c93f82f694ee998bee72999870aab~mv2.jpg

211 ms

0cdb49_9b27a6835752467eb1e0c05d4d635f7d~mv2.jpg

0cdb49_9b27a6835752467eb1e0c05d4d635f7d~mv2.jpg

211 ms

087452_eccf7a31c00f4966973d9fb1e7f7e148~mv2.jpg

087452_eccf7a31c00f4966973d9fb1e7f7e148~mv2.jpg

212 ms

087452_40c7010999134128a7fdb19fb45d8f7c~mv2.jpg

087452_40c7010999134128a7fdb19fb45d8f7c~mv2.jpg

210 ms

0cdb49_2a3d7e8b6e06493b9fbfe3270636ffdc~mv2.jpg

0cdb49_2a3d7e8b6e06493b9fbfe3270636ffdc~mv2.jpg

209 ms

087452_57aed32ad05c49f487fc480e0c7c7576~mv2.jpg

087452_57aed32ad05c49f487fc480e0c7c7576~mv2.jpg

211 ms

0cdb49_5bef1a7fe9d44aaa8853fd0a6f0c40ed~mv2.jpg

0cdb49_5bef1a7fe9d44aaa8853fd0a6f0c40ed~mv2.jpg

215 ms

0cdb49_16a676656d8b48b6a6fa2c241b840207~mv2.jpg

0cdb49_16a676656d8b48b6a6fa2c241b840207~mv2.jpg

215 ms

0cdb49_bc2bd6ef36704989a6aa882feb42abbe~mv2.png

0cdb49_bc2bd6ef36704989a6aa882feb42abbe~mv2.png

213 ms

0cdb49_2983ab2b4714476b84cf29f1fee1459e~mv2.jpg

0cdb49_2983ab2b4714476b84cf29f1fee1459e~mv2.jpg

215 ms

0cdb49_687b8d39b5d04a57bf8cd6b11a43adea~mv2.jpg

0cdb49_687b8d39b5d04a57bf8cd6b11a43adea~mv2.jpg

215 ms

0cdb49_21de9549494c42e09cce9a42a19c8826~mv2.jpg

0cdb49_21de9549494c42e09cce9a42a19c8826~mv2.jpg

212 ms

bundle.min.js

bundle.min.js

144 ms

80de9d5d-ab5f-40ce-911b-104e51e93d7c.woff

80de9d5d-ab5f-40ce-911b-104e51e93d7c.woff

40 ms

LuloCleanW05-OneBold.woff

LuloCleanW05-OneBold.woff

40 ms

e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff

e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff

38 ms

61bd362e-7162-46bd-b67e-28f366c4afbe.woff

61bd362e-7162-46bd-b67e-28f366c4afbe.woff

39 ms

AvenirLTW05-85Heavy.woff

AvenirLTW05-85Heavy.woff

38 ms

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

38 ms

Accessibility Review

intimar.in accessibility score

100

Accessibility Issues

Best Practices

intimar.in best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

intimar.in SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Intimar.in 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 Intimar.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.

Social Sharing Optimization

intimar.in

Open Graph data is detected on the main page of Intimar. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: