Tools & Wizards About Us
worldwidesms.net screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

worldwidesms.net

Bulk SMS Worldwide | Cheap, Best Bulk SMS Service & Gateway Provider in Nigeria, Worldwide | Bulk SMS Nigeria | WorldWideSMS

Page Load Speed

9.7 sec in total

First Response

375 ms

Resources Loaded

8.9 sec

Page Rendered

464 ms

worldwidesms.net screenshot

About Website

Welcome to worldwidesms.net homepage info - get ready to check Worldwide SMS best content right away, or after learning these important things about worldwidesms.net

Get Cheap Bulk SMS Nigeria to send Worldwide messaging to all networks. WorldWideSMS offers reliable Bulk SMS in Nigeria to the world. Our service includes Bulk SMS Gateway API, DND Delivery with Repo...

Visit worldwidesms.net

Key Findings

We analyzed Worldwidesms.net page load time and found that the first response time was 375 ms and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

worldwidesms.net performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value9.3 s

12/100

10%

TBT (Total Blocking Time)

Value510 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0.35

31/100

15%

TTI (Time to Interactive)

Value7.2 s

50/100

10%

Network Requests Diagram

worldwidesms.net

375 ms

worldwidesms.net

566 ms

www.worldwidesms.net

700 ms

settings.css

550 ms

layers.css

610 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 95% of them (71 requests) were addressed to the original Worldwidesms.net, 4% (3 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.9 sec) belongs to the original domain Worldwidesms.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (64%)

Content Size

2.4 MB

After Optimization

873.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Worldwidesms.net main page is 2.4 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. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 90.3 kB

  • Original 101.5 kB
  • After minification 81.7 kB
  • After compression 11.2 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 19.9 kB, which is 20% 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 90.3 kB or 89% of the original size.

Image Optimization

-75%

Potential reduce by 1.4 MB

  • Original 1.9 MB
  • After minification 486.8 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, Worldwide SMS needs image optimization as it can save up to 1.4 MB or 75% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 7.3 kB

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

CSS Optimization

-7%

Potential reduce by 11.1 kB

  • Original 152.3 kB
  • After minification 152.3 kB
  • After compression 141.2 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. Worldwidesms.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 41 (68%)

Requests Now

60

After Optimization

19

  • Images
  • JavaScript
  • CSS

The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Worldwide SMS. 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 16 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

worldwidesms.net

worldwidesms.net

375 ms

worldwidesms.net

worldwidesms.net

566 ms

www.worldwidesms.net

www.worldwidesms.net

700 ms

settings.css

settings.css

550 ms

layers.css

layers.css

610 ms

navigation.css

navigation.css

475 ms

demo-landing.css

demo-landing.css

1052 ms

css

css

33 ms

bootstrap.min.css

bootstrap.min.css

1118 ms

all.min.css

all.min.css

1460 ms

animate.min.css

animate.min.css

822 ms

simple-line-icons.min.css

simple-line-icons.min.css

1613 ms

owl.carousel.min.css

owl.carousel.min.css

1277 ms

owl.theme.default.min.css

owl.theme.default.min.css

1402 ms

magnific-popup.min.css

magnific-popup.min.css

2127 ms

theme.css

theme.css

2397 ms

theme-elements.css

theme-elements.css

1883 ms

default.css

default.css

1961 ms

bottom-website.css

bottom-website.css

2925 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

3316 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

2914 ms

modernizr.min.js

modernizr.min.js

2990 ms

jquery.min.js

jquery.min.js

3758 ms

jquery.appear.min.js

jquery.appear.min.js

3297 ms

jquery.easing.min.js

jquery.easing.min.js

3176 ms

jquery.cookie.min.js

jquery.cookie.min.js

3649 ms

popper.min.js

popper.min.js

3302 ms

bootstrap.min.js

bootstrap.min.js

3402 ms

common.min.js

common.min.js

4338 ms

jquery.validate.min.js

jquery.validate.min.js

3664 ms

jquery.easypiechart.min.js

jquery.easypiechart.min.js

3966 ms

jquery.gmap.min.js

jquery.gmap.min.js

3734 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

4726 ms

jquery.isotope.min.js

jquery.isotope.min.js

3973 ms

owl.carousel.min.js

owl.carousel.min.js

4134 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

4541 ms

jquery.vide.min.js

jquery.vide.min.js

4805 ms

vivus.min.js

vivus.min.js

4452 ms

theme.js

theme.js

4892 ms

custom.html

custom.html

4809 ms

theme.init.js

theme.init.js

4331 ms

drift.js

drift.js

4270 ms

wwwslogoname1.png

wwwslogoname1.png

4556 ms

wwshome-top-banner1.pngs

wwshome-top-banner1.pngs

4158 ms

wwshome-top-banner2.jpgs

wwshome-top-banner2.jpgs

4032 ms

worldwidesms-top-photo1.png

worldwidesms-top-photo1.png

4892 ms

worldwidesms-top-photo2.png

worldwidesms-top-photo2.png

4515 ms

wwsms-duplicate-removal.png

wwsms-duplicate-removal.png

4288 ms

wwsms-quality-sms-gateway.png

wwsms-quality-sms-gateway.png

4165 ms

wwsms-online-phonebook.png

wwsms-online-phonebook.png

3685 ms

wwsms-unlimited-recipients.png

wwsms-unlimited-recipients.png

3497 ms

wwsms-send-sms-schduler.png

wwsms-send-sms-schduler.png

3486 ms

wwsms-excel-notepad-upload.png

wwsms-excel-notepad-upload.png

3429 ms

wwsms-bulk-messaging.png

wwsms-bulk-messaging.png

3174 ms

wwsms-developer-integration-api.png

wwsms-developer-integration-api.png

2884 ms

wwsms-reseller-system.png

wwsms-reseller-system.png

2911 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

14 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

23 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

24 ms

fa-solid-900.woff

fa-solid-900.woff

3029 ms

fa-regular-400.woff

fa-regular-400.woff

2755 ms

worldwidesms-for-businesses.png

worldwidesms-for-businesses.png

2667 ms

worldwidesms-for-developers.png

worldwidesms-for-developers.png

2910 ms

worldwidesms-client_winners-chapel-logo.png

worldwidesms-client_winners-chapel-logo.png

2811 ms

fa-brands-400.woff

fa-brands-400.woff

2841 ms

worldwidesms-client_rccg-logo.png

worldwidesms-client_rccg-logo.png

2567 ms

worldwidesms-client_salvation-ministries-logo.png

worldwidesms-client_salvation-ministries-logo.png

2703 ms

worldwidesms-client_edo-microfinance-bank-logo.png

worldwidesms-client_edo-microfinance-bank-logo.png

2451 ms

worldwidesms-client_waziri-umaru-federal-polythenic-logo.png

worldwidesms-client_waziri-umaru-federal-polythenic-logo.png

2603 ms

worldwidesms-client_sir-yahaya-memorial-hospital-logo.png

worldwidesms-client_sir-yahaya-memorial-hospital-logo.png

2357 ms

worldwidesms-client_nysc-logo.png

worldwidesms-client_nysc-logo.png

2375 ms

pencil-blue-line.png

pencil-blue-line.png

2694 ms

worldwidesms.net-footer-logo.png

worldwidesms.net-footer-logo.png

2307 ms

wwshome-top-banner1.pngs

wwshome-top-banner1.pngs

1587 ms

revicons90c6.woff

revicons90c6.woff

2106 ms

Accessibility Review

worldwidesms.net accessibility score

83

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

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

Best Practices

worldwidesms.net 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

worldwidesms.net 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

    EN

  • Encoding

    UTF-8

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

worldwidesms.net

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