Tools & Wizards About Us
api.nusasms.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

api.nusasms.com

SMS API NusaSMS Untuk Integrasi dengan Sistem Eksternal

Page Load Speed

7.2 sec in total

First Response

468 ms

Resources Loaded

5.8 sec

Page Rendered

877 ms

api.nusasms.com screenshot

About Website

Visit api.nusasms.com now to see the best up-to-date API NusaSMS content for Indonesia and also check out these interesting facts you probably never knew about api.nusasms.com

SMS API memungkinkan pengiriman SMS dapat dilakukan secara langsung pada aplikasi/database Perusahaan dengan mengintegrasikannya dengan API NusaSMS

Visit api.nusasms.com

Key Findings

We analyzed Api.nusasms.com page load time and found that the first response time was 468 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.

Performance Metrics

api.nusasms.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.037

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

468 ms

2455 ms

formidableforms.css

234 ms

animate.css

468 ms

screen.min.css

697 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Api.nusasms.com, 27% (13 requests) were made to Embed.tawk.to and 13% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Nusasms.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 241.9 kB (28%)

Content Size

851.0 kB

After Optimization

609.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 162.4 kB

  • Original 197.0 kB
  • After minification 195.7 kB
  • After compression 34.6 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 162.4 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 10.0 kB

  • Original 225.1 kB
  • After minification 215.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. API NusaSMS images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 57.8 kB

  • Original 381.0 kB
  • After minification 381.0 kB
  • After compression 323.2 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 57.8 kB or 15% of the original size.

CSS Optimization

-24%

Potential reduce by 11.7 kB

  • Original 47.8 kB
  • After minification 47.8 kB
  • After compression 36.1 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. Api.nusasms.com needs all CSS files to be minified and compressed as it can save up to 11.7 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (69%)

Requests Now

39

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

468 ms

2455 ms

formidableforms.css

formidableforms.css

234 ms

animate.css

animate.css

468 ms

screen.min.css

screen.min.css

697 ms

trp-floater-language-switcher.css

trp-floater-language-switcher.css

699 ms

trp-language-switcher.css

trp-language-switcher.css

700 ms

jquery.min.js

jquery.min.js

930 ms

jquery-migrate.min.js

jquery-migrate.min.js

698 ms

ays-pb-public.js

ays-pb-public.js

699 ms

ays-pb-public-min.css

ays-pb-public-min.css

924 ms

front.min.js

front.min.js

924 ms

scripts.min.js

scripts.min.js

1391 ms

smoothscroll.js

smoothscroll.js

924 ms

common.js

common.js

1073 ms

sticky-elements.js

sticky-elements.js

1621 ms

logo-ceper.png

logo-ceper.png

235 ms

logo-long-43.png

logo-long-43.png

234 ms

login-logo-300x116.png

login-logo-300x116.png

234 ms

t_FDCF53BE-43E7-55E4-6FA8-BAD8F8B52781.jpg

t_FDCF53BE-43E7-55E4-6FA8-BAD8F8B52781.jpg

697 ms

callback-api-dr-262x300.jpg

callback-api-dr-262x300.jpg

467 ms

url-calback-300x171.jpg

url-calback-300x171.jpg

467 ms

SMSInbox-1.jpg

SMSInbox-1.jpg

468 ms

SMSInboxActivity-1.jpg

SMSInboxActivity-1.jpg

658 ms

id_ID.png

id_ID.png

698 ms

en_US.png

en_US.png

698 ms

default

default

169 ms

modules.woff

modules.woff

591 ms

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwARZtRR23w.woff

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwARZtRR23w.woff

23 ms

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwARZtRR23z.ttf

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwARZtRR23z.ttf

28 ms

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAkJxRR23w.woff

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAkJxRR23w.woff

38 ms

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAkJxRR23z.ttf

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAkJxRR23z.ttf

42 ms

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAopxRR23w.woff

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAopxRR23w.woff

40 ms

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAopxRR23z.ttf

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAopxRR23z.ttf

41 ms

et-divi-dynamic-3438-late.css

et-divi-dynamic-3438-late.css

778 ms

style.min.css

style.min.css

236 ms

twk-arr-find-polyfill.js

twk-arr-find-polyfill.js

57 ms

twk-object-values-polyfill.js

twk-object-values-polyfill.js

106 ms

twk-event-polyfill.js

twk-event-polyfill.js

104 ms

twk-entries-polyfill.js

twk-entries-polyfill.js

89 ms

twk-iterator-polyfill.js

twk-iterator-polyfill.js

89 ms

twk-promise-polyfill.js

twk-promise-polyfill.js

91 ms

twk-main.js

twk-main.js

67 ms

twk-vendor.js

twk-vendor.js

83 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

104 ms

twk-chunk-common.js

twk-chunk-common.js

94 ms

twk-runtime.js

twk-runtime.js

103 ms

twk-app.js

twk-app.js

153 ms

Accessibility Review

api.nusasms.com accessibility score

71

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

api.nusasms.com best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

api.nusasms.com SEO score

100

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    ID

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Api.nusasms.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed language. Our system also found out that Api.nusasms.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

api.nusasms.com

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