Tools & Wizards About Us
imimobile.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

imimobile.com

Webex CPaaS Solutions | Cloud Communications Platform

Page Load Speed

4.8 sec in total

First Response

167 ms

Resources Loaded

2.9 sec

Page Rendered

1.7 sec

imimobile.com screenshot

About Website

Visit imimobile.com now to see the best up-to-date Imimobile content for United States and also check out these interesting facts you probably never knew about imimobile.com

Automate your end-to-end journeys on a centralized cloud communications platform for smarter interactions with every customer. 16+ channels including SMS, RCS, WhatsApp Business, Google Business Messa...

Visit imimobile.com

Key Findings

We analyzed Imimobile.com page load time and found that the first response time was 167 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

imimobile.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

46/100

25%

SI (Speed Index)

Value8.8 s

15/100

10%

TBT (Total Blocking Time)

Value5,860 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value25.0 s

0/100

10%

Network Requests Diagram

imimobile.com

167 ms

imimobile.com

341 ms

cpaas.webex.com

542 ms

gtm.js

78 ms

tailwind.css

226 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Imimobile.com, 19% (12 requests) were made to Google-analytics.com and 16% (10 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (542 ms) relates to the external source Cpaas.webex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 339.4 kB (41%)

Content Size

817.9 kB

After Optimization

478.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Imimobile.com main page is 817.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. HTML takes 343.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 279.2 kB

  • Original 343.7 kB
  • After minification 301.4 kB
  • After compression 64.4 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 42.2 kB, which is 12% 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 279.2 kB or 81% of the original size.

Image Optimization

-11%

Potential reduce by 10.3 kB

  • Original 94.4 kB
  • After minification 84.1 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. Obviously, Imimobile needs image optimization as it can save up to 10.3 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-11%

Potential reduce by 32.9 kB

  • Original 303.8 kB
  • After minification 303.8 kB
  • After compression 270.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 32.9 kB or 11% of the original size.

CSS Optimization

-22%

Potential reduce by 17.0 kB

  • Original 76.0 kB
  • After minification 59.1 kB
  • After compression 59.0 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. Imimobile.com needs all CSS files to be minified and compressed as it can save up to 17.0 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (78%)

Requests Now

51

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

imimobile.com

imimobile.com

167 ms

imimobile.com

imimobile.com

341 ms

cpaas.webex.com

cpaas.webex.com

542 ms

gtm.js

gtm.js

78 ms

tailwind.css

tailwind.css

226 ms

iodine.min.umd.js

iodine.min.umd.js

42 ms

gsap.min.js

gsap.min.js

42 ms

ScrollTrigger.min.js

ScrollTrigger.min.js

54 ms

TextPlugin.min.js

TextPlugin.min.js

60 ms

swiper-bundle.min.css

swiper-bundle.min.css

51 ms

swiper-custom.css

swiper-custom.css

337 ms

swiper-bundle.min.js

swiper-bundle.min.js

70 ms

cdn.min.js

cdn.min.js

49 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

30 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

57 ms

site.js

site.js

286 ms

lazysizes.min.js

lazysizes.min.js

284 ms

ctm-core.js

ctm-core.js

178 ms

js

js

78 ms

analytics.js

analytics.js

37 ms

destination

destination

126 ms

webex-logo-reverse.svg

webex-logo-reverse.svg

108 ms

webex-wordmark-black.svg

webex-wordmark-black.svg

211 ms

cpaas-solutions-black.svg

cpaas-solutions-black.svg

309 ms

gartner-mq-cpass-promotion.jpg

gartner-mq-cpass-promotion.jpg

363 ms

linkedin.svg

linkedin.svg

361 ms

twitter.svg

twitter.svg

360 ms

-lBqo5g4ESk

-lBqo5g4ESk

310 ms

iframe_api

iframe_api

237 ms

destination

destination

34 ms

97191778.js

97191778.js

33 ms

www-player.css

www-player.css

55 ms

www-embed-player.js

www-embed-player.js

81 ms

base.js

base.js

113 ms

www-widgetapi.js

www-widgetapi.js

103 ms

id

id

187 ms

ad_status.js

ad_status.js

180 ms

Create

Create

81 ms

qoe

qoe

53 ms

4FCBsbVWt5jZVKm36Bs_QtpgBkunTUSSklJnPgMburg.js

4FCBsbVWt5jZVKm36Bs_QtpgBkunTUSSklJnPgMburg.js

48 ms

embed.js

embed.js

17 ms

-lBqo5g4ESk

-lBqo5g4ESk

291 ms

collect

collect

132 ms

collect

collect

208 ms

collect

collect

221 ms

collect

collect

220 ms

collect

collect

218 ms

collect

collect

250 ms

collect

collect

251 ms

collect

collect

253 ms

collect

collect

374 ms

collect

collect

373 ms

collect

collect

372 ms

ad_status.js

ad_status.js

131 ms

src=12804220;type=webex0;cat=webex00;ord=4771423567482;npa=1;pscdl=denied;frm=0;gtm=45fe4580v9181781477z871974470za201;gcs=G100;gcd=13p3p3p3p5;dma_cps=-;dma=0;epver=2;~oref=https%3A%2F%2Fcpaas.webex.com%2F

src=12804220;type=webex0;cat=webex00;ord=4771423567482;npa=1;pscdl=denied;frm=0;gtm=45fe4580v9181781477z871974470za201;gcs=G100;gcd=13p3p3p3p5;dma_cps=-;dma=0;epver=2;~oref=https%3A%2F%2Fcpaas.webex.com%2F

251 ms

landing

landing

249 ms

4FCBsbVWt5jZVKm36Bs_QtpgBkunTUSSklJnPgMburg.js

4FCBsbVWt5jZVKm36Bs_QtpgBkunTUSSklJnPgMburg.js

54 ms

embed.js

embed.js

31 ms

Create

Create

164 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

140 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

141 ms

id

id

124 ms

Accessibility Review

imimobile.com accessibility score

96

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

Links do not have a discernible name

Best Practices

imimobile.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

imimobile.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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 Imimobile.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 Imimobile.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.

Social Sharing Optimization

imimobile.com

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