Tools & Wizards About Us
intlcx.com screenshot

Report Summary

  • 77

    Performance

    Renders faster than
    84% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

intlcx.com

ICX

Page Load Speed

1.7 sec in total

First Response

78 ms

Resources Loaded

1.2 sec

Page Rendered

423 ms

intlcx.com screenshot

About Website

Click here to check amazing Intlcx content for India. Otherwise, check out these important facts you probably never knew about intlcx.com

We make it easy for businesses to send SMS API or SMPP. We terminate each SMS to US as low as 0.001/message. Save time and money buying from the industry experts

Visit intlcx.com

Key Findings

We analyzed Intlcx.com page load time and found that the first response time was 78 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

intlcx.com performance score

77

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

87/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

intlcx.com

78 ms

www.intlcx.com

77 ms

bootstrap.min.css

108 ms

fontawesome-all.min.css

59 ms

swiper.min.css

74 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 72% of them (38 requests) were addressed to the original Intlcx.com, 25% (13 requests) were made to Embed.tawk.to and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (340 ms) relates to the external source Embed.tawk.to.

Page Optimization Overview & Recommendations

Page size can be reduced by 60.4 kB (18%)

Content Size

338.7 kB

After Optimization

278.4 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Intlcx.com main page is 338.7 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. 55% of websites need less resources to load. Javascripts take 259.1 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 35.0 kB

  • Original 39.9 kB
  • After minification 27.1 kB
  • After compression 5.0 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 12.8 kB, which is 32% 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 35.0 kB or 88% of the original size.

JavaScript Optimization

-9%

Potential reduce by 23.4 kB

  • Original 259.1 kB
  • After minification 259.1 kB
  • After compression 235.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. This website has mostly compressed JavaScripts.

CSS Optimization

-5%

Potential reduce by 2.0 kB

  • Original 39.7 kB
  • After minification 37.7 kB
  • After compression 37.7 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. Intlcx.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 25 (49%)

Requests Now

51

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

intlcx.com

intlcx.com

78 ms

www.intlcx.com

www.intlcx.com

77 ms

bootstrap.min.css

bootstrap.min.css

108 ms

fontawesome-all.min.css

fontawesome-all.min.css

59 ms

swiper.min.css

swiper.min.css

74 ms

main.css

main.css

85 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

118 ms

popper.min.js

popper.min.js

59 ms

bootstrap.min.js

bootstrap.min.js

153 ms

swiper.min.js

swiper.min.js

201 ms

jquery.ajaxchimp.min.js

jquery.ajaxchimp.min.js

122 ms

wb.swiper-init.js

wb.swiper-init.js

124 ms

wb.ajaxchimp-init.js

wb.ajaxchimp-init.js

207 ms

js

js

208 ms

main-min.js

main-min.js

207 ms

inter.css

inter.css

70 ms

logo.svg

logo.svg

93 ms

hero_image.webp

hero_image.webp

96 ms

icn_fluxo_influencer.svg

icn_fluxo_influencer.svg

95 ms

icn_fluxo_chart.svg

icn_fluxo_chart.svg

94 ms

icn_fluxo_cloud.svg

icn_fluxo_cloud.svg

93 ms

Voip.webp

Voip.webp

97 ms

icn_fluxo_stacks.svg

icn_fluxo_stacks.svg

120 ms

DID.webp

DID.webp

154 ms

SMSC.webp

SMSC.webp

152 ms

icn_fluxo_users.svg

icn_fluxo_users.svg

123 ms

icn_fluxo_group-users.svg

icn_fluxo_group-users.svg

120 ms

icn_fluxo_office.svg

icn_fluxo_office.svg

129 ms

icn_fluxo_speaker.svg

icn_fluxo_speaker.svg

172 ms

icn_fluxo_customer-support.svg

icn_fluxo_customer-support.svg

164 ms

logo-footer.svg

logo-footer.svg

175 ms

default

default

261 ms

fa-solid-900.woff

fa-solid-900.woff

101 ms

fa-regular-400.woff

fa-regular-400.woff

124 ms

fa-brands-400.woff

fa-brands-400.woff

134 ms

fa-solid-900.ttf

fa-solid-900.ttf

68 ms

fa-regular-400.ttf

fa-regular-400.ttf

64 ms

fa-brands-400.ttf

fa-brands-400.ttf

71 ms

fa-solid-900.svg

fa-solid-900.svg

63 ms

fa-regular-400.svg

fa-regular-400.svg

89 ms

fa-brands-400.svg

fa-brands-400.svg

70 ms

twk-arr-find-polyfill.js

twk-arr-find-polyfill.js

60 ms

twk-object-values-polyfill.js

twk-object-values-polyfill.js

226 ms

twk-event-polyfill.js

twk-event-polyfill.js

117 ms

twk-entries-polyfill.js

twk-entries-polyfill.js

242 ms

twk-iterator-polyfill.js

twk-iterator-polyfill.js

228 ms

twk-promise-polyfill.js

twk-promise-polyfill.js

226 ms

twk-main.js

twk-main.js

121 ms

twk-vendor.js

twk-vendor.js

209 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

243 ms

twk-chunk-common.js

twk-chunk-common.js

340 ms

twk-runtime.js

twk-runtime.js

279 ms

twk-app.js

twk-app.js

291 ms

Accessibility Review

intlcx.com accessibility score

89

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

intlcx.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

intlcx.com SEO score

98

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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

intlcx.com

Open Graph description is not detected on the main page of Intlcx. 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: