SWAZI.NET Swaziland Post and Telecommunications Corporation (SPTC)


swazi.net website information.

swazi.net domain name is registered by .NET top-level domain registry. See the other sites registred in .NET domain zone.

No name server records were found.

According to Alexa traffic rank the highest website swazi.net position was 104637 (in the world). The lowest Alexa rank position was 998635. Current position of swazi.net in Alexa rank database is below 1 million.

Website swazi.net Desktop speed measurement score (49/100) is better than the results of 22.8% of other sites shows that the page desktop performance can be improved.

swazi.net Mobile usability score (59/100) is better than the results of 2.69% of other sites and shows that the page mobile usability is poor and can be improved.

Mobile speed measurement score of swazi.net (78/100) is better than the results of 86.92% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
May-05-2024 N/AN/A
May-04-2024 N/AN/A
May-03-2024 N/AN/A
May-02-2024 N/AN/A
May-01-2024 N/AN/A
Apr-30-2024 N/AN/A
Apr-29-2024 N/AN/A

Advertisement

swazi.net Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.



swazi.net whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


Domain Name: SWAZI.NET
Registry Domain ID: 20936975_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.corehub.net
Registrar URL: http://corehub.net
Updated Date: 2013-03-15T19:35:35Z
Creation Date: 2000-02-29T07:26:07Z
Registry Expiry Date: 2023-03-01T07:26:07Z
Registrar: Corehub, S.R.L.
Registrar IANA ID: 15
Registrar Abuse Contact Email: abuse@corehub.net
Registrar Abuse Contact Phone: +34935275235
Domain Status: ok https://icann.org/epp#ok
Name Server: NS1.SWAZI.NET
Name Server: NS2.SWAZI.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2021-11-26T07:05:04Z

swazi.net server information

Servers Location

IP Address
Country
Region
City

swazi.net desktop page speed rank

Last tested: 2019-01-12


Desktop Speed Bad
49/100

swazi.net Desktop Speed Test Quick Summary


priority - 78 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 758.4KiB (77% reduction).

Compressing and resizing http://swazi.net/csi/charitycup/charity.jpg could save 190.2KiB (91% reduction).
Losslessly compressing http://swazi.net/graphics/customerarea.png could save 58.5KiB (91% reduction).
Losslessly compressing http://swazi.net/graphics/twitter.png could save 53.7KiB (92% reduction).
Losslessly compressing http://swazi.net/graphics/email.png could save 53.5KiB (95% reduction).
Losslessly compressing http://swazi.net/homeslider/btn_next.png could save 52.9KiB (99% reduction).
Losslessly compressing http://swazi.net/graphics/linkedin.png could save 52.6KiB (92% reduction).
Losslessly compressing http://swazi.net/graphics/facebook.png could save 52.3KiB (93% reduction).
Compressing and resizing http://swazi.net/news/LetterCompetition.jpg could save 50.9KiB (96% reduction).
Losslessly compressing http://swazi.net/homeslider/btn_pause.png could save 50KiB (99% reduction).
Losslessly compressing http://swazi.net/graphics/fax.png could save 49KiB (97% reduction).
Losslessly compressing http://swazi.net/footer/phutfumani.jpg could save 12.5KiB (74% reduction).
Losslessly compressing http://swazi.net/footer/swazi_net.jpg could save 12.5KiB (75% reduction).
Losslessly compressing http://swazi.net/footer/swaziltelco.jpg could save 12.5KiB (66% reduction).
Losslessly compressing http://swazi.net/footer/swazipost.jpg could save 12.5KiB (76% reduction).
Losslessly compressing http://swazi.net/homeslider/gwalamo.jpg could save 12.5KiB (13% reduction).
Losslessly compressing http://swazi.net/logo/sptc.jpg could save 12.5KiB (53% reduction).
Losslessly compressing http://swazi.net/swazipost/stamps/sets/cover.jpg could save 12.5KiB (18% reduction).
Losslessly compressing http://swazi.net/graphics/charity.jpg could save 7KiB (93% reduction).

priority - 15 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://swazi.net/csi/charitycup/charity.jpg (expiration not specified)
http://swazi.net/css/homeslider.css (expiration not specified)
http://swazi.net/css/style.css (expiration not specified)
http://swazi.net/footer/phutfumani.jpg (expiration not specified)
http://swazi.net/footer/swazi_net.jpg (expiration not specified)
http://swazi.net/footer/swaziltelco.jpg (expiration not specified)
http://swazi.net/footer/swazipost.jpg (expiration not specified)
http://swazi.net/graphics/charity.jpg (expiration not specified)
http://swazi.net/graphics/chat.png (expiration not specified)
http://swazi.net/graphics/customerarea.png (expiration not specified)
http://swazi.net/graphics/email.png (expiration not specified)
http://swazi.net/graphics/emailf.png (expiration not specified)
http://swazi.net/graphics/facebook.png (expiration not specified)
http://swazi.net/graphics/fax.png (expiration not specified)
http://swazi.net/graphics/fbF.png (expiration not specified)
http://swazi.net/graphics/linkedin.png (expiration not specified)
http://swazi.net/graphics/tollfree.png (expiration not specified)
http://swazi.net/graphics/twitter.png (expiration not specified)
http://swazi.net/graphics/twitterF.png (expiration not specified)
http://swazi.net/homeslider/btn_back.png (expiration not specified)
http://swazi.net/homeslider/btn_next.png (expiration not specified)
http://swazi.net/homeslider/btn_pause.png (expiration not specified)
http://swazi.net/homeslider/gwalamo.jpg (expiration not specified)
http://swazi.net/js/hmenuscript.js (expiration not specified)
http://swazi.net/js/homesliderscript.js (expiration not specified)
http://swazi.net/js/homesliderscript2.js (expiration not specified)
http://swazi.net/js/internalsearchengine.js (expiration not specified)
http://swazi.net/logo/sptc.jpg (expiration not specified)
http://swazi.net/news/LetterCompetition.jpg (expiration not specified)
http://swazi.net/swazipost/stamps/sets/cover.jpg (expiration not specified)

priority - 9 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 85.7KiB (70% reduction).

Compressing http://swazi.net/js/homesliderscript2.js could save 45.8KiB (65% reduction).
Compressing http://swazi.net/css/style.css could save 20.4KiB (79% reduction).
Compressing http://swazi.net/home.php could save 15.5KiB (76% reduction).
Compressing http://swazi.net/js/homesliderscript.js could save 2.6KiB (66% reduction).
Compressing http://swazi.net/css/homeslider.css could save 827B (60% reduction).
Compressing http://swazi.net/js/hmenuscript.js could save 652B (51% reduction).

priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

http://swazi.net/js/hmenuscript.js
http://swazi.net/js/homesliderscript2.js
http://swazi.net/js/homesliderscript.js
http://swazi.net/js/internalsearchengine.js

Optimize CSS Delivery of the following:

http://swazi.net/css/style.css
http://swazi.net/css/homeslider.css

priority - 2 Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 24% of the final above-the-fold content could be rendered with the full HTML response.

priority - 1 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 5.2KiB (20% reduction).

Minifying http://swazi.net/css/style.css could save 5.2KiB (20% reduction).

priority - 0 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 4.3KiB (22% reduction).

Minifying http://swazi.net/home.php could save 4.3KiB (22% reduction).

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 2.1KiB (3% reduction).

Minifying http://swazi.net/js/homesliderscript.js could save 1.4KiB (38% reduction).
Minifying http://swazi.net/js/homesliderscript2.js could save 658B (1% reduction).

swazi.net Desktop Resources

Total Resources35
Number of Hosts1
Static Resources30
JavaScript Resources4
CSS Resources2

swazi.net Desktop Resource Breakdown

swazi.net mobile page speed rank

Last tested: 2019-01-12


Mobile Speed Medium
78/100

swazi.net Mobile Speed Test Quick Summary


priority - 10 Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://swazi.net/
http://www.sptc.co.sz/m
http://www.sptc.co.sz/m/

priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Optimize CSS Delivery of the following:

http://www.sptc.co.sz/m/mstyle.css

priority - 4 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 42.9KiB (50% reduction).

Losslessly compressing http://www.sptc.co.sz/m/graphics/menuitem.png could save 28.6KiB (99% reduction).
Losslessly compressing http://www.sptc.co.sz/m/adverts/charity.jpg could save 11KiB (33% reduction).
Losslessly compressing http://www.sptc.co.sz/logo/m-sptc.jpg could save 3.4KiB (15% reduction).

priority - 4 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://www.sptc.co.sz/logo/m-sptc.jpg (expiration not specified)
http://www.sptc.co.sz/m/adverts/charity.jpg (expiration not specified)
http://www.sptc.co.sz/m/graphics/menuitem.png (expiration not specified)
http://www.sptc.co.sz/m/graphics/next.png (expiration not specified)
http://www.sptc.co.sz/m/mstyle.css (expiration not specified)

priority - 1 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 11.7KiB (73% reduction).

Compressing http://www.sptc.co.sz/m/mstyle.css could save 10.9KiB (76% reduction).
Compressing http://www.sptc.co.sz/m/ could save 868B (50% reduction).

priority - 0 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 3.4KiB (24% reduction).

Minifying http://www.sptc.co.sz/m/mstyle.css could save 3.4KiB (24% reduction).

swazi.net Mobile Resources

Total Resources8
Number of Hosts2
Static Resources5
CSS Resources1

swazi.net Mobile Resource Breakdown

swazi.net mobile page usability

Last tested: 2019-01-12


Mobile Usability Bad
59/100

swazi.net Mobile Usability Test Quick Summary


priority - 40 Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

*CHARITY CUP VOTING renders only 5 pixels tall (18 CSS pixels).

*LATEST VOTING RESULTS renders only 5 pixels tall (18 CSS pixels).

FIND A POST OFFICE and 6 others render only 5 pixels tall (18 CSS pixels).

© 2015 Swazila…ghts Reserved. renders only 3 pixels tall (12 CSS pixels).

priority - 24 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="http://voting.sptc.co.sz/2015/">*CHARITY CUP VOTING</a> is close to 1 other tap targets.

The tap target <a href="stats.php">*LATEST VOTING RESULTS</a> is close to 2 other tap targets.

The tap target <a href="outages/index.php">NETWORK UPDATES</a> and 6 others are close to other tap targets.

priority - 10 Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

swazi.net similar domains

Similar domains:
www.swazi.com
www.swazi.net
www.swazi.org
www.swazi.info
www.swazi.biz
www.swazi.us
www.swazi.mobi
www.wazi.net
www.swazi.net
www.wwazi.net
www.swwazi.net
www.wswazi.net
www.ewazi.net
www.sewazi.net
www.eswazi.net
www.dwazi.net
www.sdwazi.net
www.dswazi.net
www.zwazi.net
www.szwazi.net
www.zswazi.net
www.xwazi.net
www.sxwazi.net
www.xswazi.net
www.awazi.net
www.sawazi.net
www.aswazi.net
www.sazi.net
www.sqazi.net
www.swqazi.net
www.sqwazi.net
www.saazi.net
www.swaazi.net
www.ssazi.net
www.swsazi.net
www.sswazi.net
www.seazi.net
www.sweazi.net
www.swzi.net
www.swqzi.net
www.swaqzi.net
www.swwzi.net
www.swawzi.net
www.swszi.net
www.swaszi.net
www.swzzi.net
www.swazzi.net
www.swzazi.net
www.swai.net
www.swaxi.net
www.swazxi.net
www.swaxzi.net
www.swasi.net
www.swazsi.net
www.swaai.net
www.swazai.net
www.swaz.net
www.swazu.net
www.swaziu.net
www.swazui.net
www.swazj.net
www.swazij.net
www.swazji.net
www.swazk.net
www.swazik.net
www.swazki.net
www.swazo.net
www.swazio.net
www.swazoi.net

swazi.net Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


swazi.net TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.