Wormex.Io - Info wormex.io

wormex.io receives about 318 unique visitors and 635 (2.00 per visitor) page views per day which should earn about $2.59/day from advertising revenue. Estimated site value is $1,891.51. According to Alexa Traffic Rank wormex.io is ranked number 3,545,871 in the world and 7.0E-6% of global Internet users visit it. Site is hosted in Australia and links to network IP address 103.224.182.252. This server supports HTTPS and doesn't support HTTP/2.

About - wormex.io


Technologies used on Website

Web Servers
Nginx
Reverse Proxy
Nginx

wormex.io Profile

Title: wormex.io - This website is for sale! - cloud server monitoring Resources and Information.
Description: This website is for sale! wormex.io is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, wormex.io has it all. We hope you find what you are searching for!
Last update was 4 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with wormex.io in any way. Only publicly available statistics data are displayed.

How popular is wormex.io?

318 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
318
Monthly Unique Visitors:
7,632
Pages per Visit:
2.00
Daily Pageviews:
635
Alexa Rank:
3,545,871 visit alexa
Alexa Reach:
7.0E-6%   (of global internet users)
Avg. visit duration:
00:00
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  wormex.io
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is wormex.io?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
wormex.io
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
wormex.io
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much wormex.io can earn?

Daily Revenue:
$2.59
Monthly Revenue:
$77.70
Yearly Revenue:
$945.35
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do wormex.io lose due to Adblock?

Daily Revenue Loss:
n/a
Monthly Revenue Loss:
n/a
Yearly Revenue Loss:
n/a
Daily Pageviews Blocked:
n/a
Monthly Pageviews Blocked:
n/a
Yearly Pageviews Blocked:
n/a
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is wormex.io worth?

Website Value:
$1,891.51

+ Where is wormex.io hosted?

Server IP:
103.224.182.252
ASN:
AS133618 
ISP:
Trellian Pty. Limited 
Server Location:

Australia, AU
 

Other sites hosted on 103.224.182.252

+ How fast does wormex.io load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

98
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Time to Interactive 1.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 90 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 1.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.1 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 110 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Minimize third-party usage - Third-party code blocked the main thread for 80 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Third-Party
SizeMain-Thread Blocking Time
196 KB83 ms
1 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
672 ms
6 ms
707 ms
17 ms
733 ms
63 ms
797 ms
10 ms
814 ms
6 ms
824 ms
6 ms
835 ms
6 ms
841 ms
6 ms
884 ms
50 ms
934 ms
12 ms
956 ms
85 ms
1055 ms
112 ms
1170 ms
5 ms
1177 ms
97 ms
JavaScript execution time - 0.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
https://www.google.com/adsense/domains/caf.js
335 ms277 ms25 ms
Other
114 ms11 ms4 ms
http://ww1.wormex.io/
53 ms41 ms4 ms
Avoids enormous network payloads - Total size was 245 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.google.com/adsense/domains/caf.js
56 KB
https://www.google.com/adsense/domains/caf.js
56 KB
http://www.google.com/adsense/domains/caf.js
55 KB
http://img.sedoparking.com/js/jquery-1.11.3.custom.min.js
25 KB
http://ww1.wormex.io/
21 KB
https://www.google.com/dp/ads?r=m&client=dp-sedo80_3ph&channel=exp-0051%2Cauxa-control-2%2C445328&hl=en&adtest=off&adsafe=low&type=3&kw=cloud%20server%20monitoring&optimize_terms=off&terms=cloud%20server%20monitoring%2Cvirtualized%20server%2Chipaa%20compliant%20server%2Cvirtualization%20appliance%2Cdedicated%20server%20prices%2Ccloud%20based%20call%20center%20solutions%2Cvirtualize%20server%2Cprivate%20cloud%20hosting%2Cvirtualized%20server%20hosting%2Cvirtualization%20server&swp=as-drid-2777688820344496&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002&format=r10&num=0&output=afd_ads&domain_name=ww1.wormex.io&v=3&preload=true&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-480&dt=1573261882555&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=88&frm=0&uio=sl1sr1-st24sa18lt45&cont=rb-default&jsv=12898&rurl=http%3A%2F%2Fww1.wormex.io%2F
7 KB
https://www.google.com/dp/ads?r=m&client=dp-sedo80_3ph&channel=exp-0051%2Cauxa-control-2%2C445328&hl=en&adtest=off&adsafe=low&kw=cloud%20server%20monitoring&swp=as-drid-2777688820344496&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002&format=s&num=0&output=afd_ads&domain_name=ww1.wormex.io&v=3&preload=true&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-480&dt=1573261882536&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=50&frm=0&uio=sl1sr1-&cont=sb-default&jsv=12898&rurl=http%3A%2F%2Fww1.wormex.io%2F
7 KB
https://www.google.com/js/bg/Y127TbzHFt853-1VpJF27iywYTJTzUR5UBGBBrYp_xw.js
6 KB
https://www.google.com/js/bg/Y127TbzHFt853-1VpJF27iywYTJTzUR5UBGBBrYp_xw.js
6 KB
https://afs.googleusercontent.com/dp-sedo/bullet_lime.gif
2 KB
Minimizes main-thread work - 0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
368 ms
Other
65 ms
Style & Layout
44 ms
Script Parsing & Compilation
40 ms
Parse HTML & CSS
14 ms
Rendering
12 ms
Garbage Collection
7 ms
Avoids an excessive DOM size - 41 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
41
Maximum DOM Depth
7
Maximum Child Elements
11
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://wormex.io/)
0
http://ww1.wormex.io/
190
Keep request counts low and transfer sizes small - 16 requests • 245 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
16245 KB
Script
6204 KB
Document
538 KB
Image
33 KB
Other
20 KB
Stylesheet
00 KB
Media
00 KB
Font
00 KB
Third-party
13224 KB
Eliminate render-blocking resources - Potential savings of 30 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://img.sedoparking.com/js/jquery-1.11.3.custom.min.js
25 KB230
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://wormex.io/
0 ms314 ms0 KB0 KB302text/html
http://ww1.wormex.io/
314 ms647 ms21 KB68 KB200text/htmlDocument
http://img.sedoparking.com/js/jquery-1.11.3.custom.min.js
659 ms680 ms25 KB62 KB200application/x-javascriptScript
http://www.google.com/adsense/domains/caf.js
659 ms679 ms55 KB155 KB200text/javascriptScript
http://ww1.wormex.io/search/tsc.php?200=Mjg0MjkyOTI2&21=NjcuMjEyLjE4Ny4xMDY=&681=MTU3MzI2MTg4MmY3MzM5ZWYyYzUzOGUwOGQ5NTllYmVmOWU3NjJkM2Rl&crc=5cec6997d504bfd4555f012ab5f8a9f9d7c3f441&cv=1
723 ms851 ms0 KB0 KB200text/htmlXHR
https://www.google.com/dp/ads?r=m&client=dp-sedo80_3ph&channel=exp-0051%2Cauxa-control-2%2C445328&hl=en&adtest=off&adsafe=low&kw=cloud%20server%20monitoring&swp=as-drid-2777688820344496&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002&format=s&num=0&output=afd_ads&domain_name=ww1.wormex.io&v=3&preload=true&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-480&dt=1573261882536&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=50&frm=0&uio=sl1sr1-&cont=sb-default&jsv=12898&rurl=http%3A%2F%2Fww1.wormex.io%2F
746 ms811 ms7 KB8 KB200text/htmlDocument
http://www.gstatic.com/domainads/tracking/caf.gif?ts=1573261882526&rid=6320609
749 ms753 ms0 KB0 KB200image/gifImage
https://www.google.com/dp/ads?r=m&client=dp-sedo80_3ph&channel=exp-0051%2Cauxa-control-2%2C445328&hl=en&adtest=off&adsafe=low&type=3&kw=cloud%20server%20monitoring&optimize_terms=off&terms=cloud%20server%20monitoring%2Cvirtualized%20server%2Chipaa%20compliant%20server%2Cvirtualization%20appliance%2Cdedicated%20server%20prices%2Ccloud%20based%20call%20center%20solutions%2Cvirtualize%20server%2Cprivate%20cloud%20hosting%2Cvirtualized%20server%20hosting%2Cvirtualization%20server&swp=as-drid-2777688820344496&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002&format=r10&num=0&output=afd_ads&domain_name=ww1.wormex.io&v=3&preload=true&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-480&dt=1573261882555&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=88&frm=0&uio=sl1sr1-st24sa18lt45&cont=rb-default&jsv=12898&rurl=http%3A%2F%2Fww1.wormex.io%2F
768 ms859 ms7 KB10 KB200text/htmlDocument
http://www.gstatic.com/domainads/tracking/caf.gif?ts=1573261882552&rid=5355959
772 ms786 ms0 KB0 KB200image/gifImage
https://www.google.com/afs/ads/i/iframe.html
790 ms796 ms2 KB1 KB200text/htmlDocument
https://www.google.com/afs/ads/i/iframe.html
797 ms809 ms2 KB1 KB200text/htmlDocument
https://www.google.com/adsense/domains/caf.js
828 ms851 ms56 KB155 KB200text/javascriptScript
https://www.google.com/js/bg/Y127TbzHFt853-1VpJF27iywYTJTzUR5UBGBBrYp_xw.js
942 ms947 ms6 KB12 KB200text/javascriptScript
https://www.google.com/adsense/domains/caf.js
933 ms935 ms56 KB155 KB200text/javascriptScript
https://afs.googleusercontent.com/dp-sedo/bullet_lime.gif
995 ms1014 ms2 KB1 KB200image/gifImage
https://www.google.com/js/bg/Y127TbzHFt853-1VpJF27iywYTJTzUR5UBGBBrYp_xw.js
1029 ms1033 ms6 KB12 KB200text/javascriptScript
Uses efficient cache policy on static assets - 2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://afs.googleusercontent.com/dp-sedo/bullet_lime.gif
82800000 ms2 KB
http://img.sedoparking.com/js/jquery-1.11.3.custom.min.js
86400000 ms25 KB
Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Avoid chaining critical requests - 2 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 330 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

82
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Speed Index 3.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 4.6 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 2.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 2.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 400 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 4.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time 640 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 110 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
First Contentful Paint (3G) 5016 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Reduce JavaScript execution time - 1.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
https://www.google.com/adsense/domains/caf.js
1038 ms914 ms43 ms
Other
444 ms43 ms17 ms
http://ww1.wormex.io/
222 ms150 ms14 ms
http://img.sedoparking.com/js/jquery-1.11.3.custom.min.js
83 ms71 ms6 ms
http://www.google.com/adsense/domains/caf.js
80 ms64 ms14 ms
Avoids enormous network payloads - Total size was 245 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.google.com/adsense/domains/caf.js
56 KB
https://www.google.com/adsense/domains/caf.js
56 KB
http://www.google.com/adsense/domains/caf.js
55 KB
http://img.sedoparking.com/js/jquery-1.11.3.custom.min.js
25 KB
http://ww1.wormex.io/
20 KB
https://www.google.com/dp/ads?r=m&client=dp-sedo80_3ph&channel=exp-0050%2Cauxa-control-2%2C445328&hl=en&adtest=off&adsafe=low&type=3&kw=cloud%20server%20monitoring&optimize_terms=off&terms=cloud%20server%20monitoring%2Cvirtualized%20server%2Chipaa%20compliant%20server%2Cvirtualization%20appliance%2Cdedicated%20server%20prices%2Ccloud%20based%20call%20center%20solutions%2Cvirtualize%20server%2Cprivate%20cloud%20hosting%2Cvirtualized%20server%20hosting%2Cvirtualization%20server&swp=as-drid-2777688820344496&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002&format=r10&num=0&output=afd_ads&domain_name=ww1.wormex.io&v=3&preload=true&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-480&dt=1573261876781&u_w=412&u_h=660&biw=412&bih=660&psw=412&psh=476&frm=0&uio=sl1sr1-st22sa10lt40&cont=rb-default&jsv=12898&rurl=http%3A%2F%2Fww1.wormex.io%2F
7 KB
https://www.google.com/dp/ads?r=m&client=dp-sedo80_3ph&channel=exp-0050%2Cauxa-control-2%2C445328&hl=en&adtest=off&adsafe=low&kw=cloud%20server%20monitoring&swp=as-drid-2777688820344496&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002&format=s&num=0&output=afd_ads&domain_name=ww1.wormex.io&v=3&preload=true&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-480&dt=1573261876761&u_w=412&u_h=660&biw=412&bih=660&psw=412&psh=8&frm=0&uio=sl1sr1-&cont=sb-default&jsv=12898&rurl=http%3A%2F%2Fww1.wormex.io%2F
7 KB
https://www.google.com/js/bg/Y127TbzHFt853-1VpJF27iywYTJTzUR5UBGBBrYp_xw.js
6 KB
https://www.google.com/js/bg/Y127TbzHFt853-1VpJF27iywYTJTzUR5UBGBBrYp_xw.js
6 KB
https://afs.googleusercontent.com/dp-sedo/bullet_lime.gif
2 KB
Minimizes main-thread work - 1.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
1268 ms
Other
261 ms
Style & Layout
148 ms
Script Parsing & Compilation
104 ms
Parse HTML & CSS
54 ms
Rendering
46 ms
Garbage Collection
25 ms
Avoids an excessive DOM size - 40 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
40
Maximum DOM Depth
6
Maximum Child Elements
13
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://wormex.io/)
0
http://ww1.wormex.io/
630
Keep request counts low and transfer sizes small - 16 requests • 245 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
16245 KB
Script
6204 KB
Document
538 KB
Image
33 KB
Other
20 KB
Stylesheet
00 KB
Media
00 KB
Font
00 KB
Third-party
13224 KB
Eliminate render-blocking resources - Potential savings of 280 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://img.sedoparking.com/js/jquery-1.11.3.custom.min.js
25 KB780
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://wormex.io/
0 ms355 ms0 KB0 KB302text/html
http://ww1.wormex.io/
356 ms916 ms20 KB64 KB200text/htmlDocument
http://img.sedoparking.com/js/jquery-1.11.3.custom.min.js
930 ms951 ms25 KB62 KB200application/x-javascriptScript
http://www.google.com/adsense/domains/caf.js
930 ms955 ms55 KB155 KB200text/javascriptScript
http://ww1.wormex.io/search/tsc.php?200=Mjg0MjkyOTI2&21=NjcuMjEyLjE4Ny4xMDY=&681=MTU3MzI2MTg3Njc4NzcxMzA5MTM3ZTAyNjk0MDlmMjZjZDgwNTFkODQz&crc=a8243297c26cbc167750e53d092aa76bf247380f&cv=1
995 ms1139 ms0 KB0 KB200text/htmlXHR
https://www.google.com/dp/ads?r=m&client=dp-sedo80_3ph&channel=exp-0050%2Cauxa-control-2%2C445328&hl=en&adtest=off&adsafe=low&kw=cloud%20server%20monitoring&swp=as-drid-2777688820344496&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002&format=s&num=0&output=afd_ads&domain_name=ww1.wormex.io&v=3&preload=true&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-480&dt=1573261876761&u_w=412&u_h=660&biw=412&bih=660&psw=412&psh=8&frm=0&uio=sl1sr1-&cont=sb-default&jsv=12898&rurl=http%3A%2F%2Fww1.wormex.io%2F
1014 ms1092 ms7 KB8 KB200text/htmlDocument
http://www.gstatic.com/domainads/tracking/caf.gif?ts=1573261876753&rid=5578248
1021 ms1026 ms0 KB0 KB200image/gifImage
https://www.google.com/dp/ads?r=m&client=dp-sedo80_3ph&channel=exp-0050%2Cauxa-control-2%2C445328&hl=en&adtest=off&adsafe=low&type=3&kw=cloud%20server%20monitoring&optimize_terms=off&terms=cloud%20server%20monitoring%2Cvirtualized%20server%2Chipaa%20compliant%20server%2Cvirtualization%20appliance%2Cdedicated%20server%20prices%2Ccloud%20based%20call%20center%20solutions%2Cvirtualize%20server%2Cprivate%20cloud%20hosting%2Cvirtualized%20server%20hosting%2Cvirtualization%20server&swp=as-drid-2777688820344496&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002&format=r10&num=0&output=afd_ads&domain_name=ww1.wormex.io&v=3&preload=true&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-480&dt=1573261876781&u_w=412&u_h=660&biw=412&bih=660&psw=412&psh=476&frm=0&uio=sl1sr1-st22sa10lt40&cont=rb-default&jsv=12898&rurl=http%3A%2F%2Fww1.wormex.io%2F
1041 ms1129 ms7 KB10 KB200text/htmlDocument
http://www.gstatic.com/domainads/tracking/caf.gif?ts=1573261876778&rid=3926940
1047 ms1051 ms0 KB0 KB200image/gifImage
https://www.google.com/afs/ads/i/iframe.html
1067 ms1077 ms2 KB1 KB200text/htmlDocument
https://www.google.com/afs/ads/i/iframe.html
1077 ms1083 ms2 KB1 KB200text/htmlDocument
https://www.google.com/adsense/domains/caf.js
1109 ms1135 ms56 KB155 KB200text/javascriptScript
https://www.google.com/adsense/domains/caf.js
1143 ms1161 ms56 KB155 KB200text/javascriptScript
https://www.google.com/js/bg/Y127TbzHFt853-1VpJF27iywYTJTzUR5UBGBBrYp_xw.js
1194 ms1199 ms6 KB12 KB200text/javascriptScript
https://afs.googleusercontent.com/dp-sedo/bullet_lime.gif
1232 ms1280 ms2 KB1 KB200image/gifImage
https://www.google.com/js/bg/Y127TbzHFt853-1VpJF27iywYTJTzUR5UBGBBrYp_xw.js
1249 ms1253 ms6 KB12 KB200text/javascriptScript
Uses efficient cache policy on static assets - 2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://afs.googleusercontent.com/dp-sedo/bullet_lime.gif
82800000 ms2 KB
http://img.sedoparking.com/js/jquery-1.11.3.custom.min.js
86400000 ms25 KB
Reduce the impact of third-party code - Third-party code blocked the main thread for 630 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Third-Party
SizeMain-Thread Blocking Time
196 KB628 ms
1 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
937 ms
8 ms
976 ms
22 ms
1005 ms
63 ms
1068 ms
12 ms
1087 ms
6 ms
1099 ms
7 ms
1106 ms
6 ms
1115 ms
7 ms
1150 ms
7 ms
1166 ms
41 ms
1219 ms
44 ms
1271 ms
99 ms
1376 ms
82 ms
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Avoid chaining critical requests - 2 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 560 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

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

Your page has 2 blocking script 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://img.sedoparking.com/js/jquery-1.11.3.custom.min.js
http://www.google.com/adsense/domains/caf.js

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.google.com/adsense/domains/caf.js (60 minutes)
https://www.google.com/adsense/domains/caf.js (60 minutes)

Optimize images

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

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

Compressing https://afs.googleusercontent.com/dp-sedo/bullet_lime.gif could save 1.1KiB (77% reduction).
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Enable compression
You have compression enabled. Learn more about enabling compression.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does wormex.io use compression?

wormex.io use gzip compression.
Original size: 68.16 KB
Compressed size: 19.92 KB
File reduced by: 48.24 KB (70%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

wormex.io supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: xn--deutschbung-zhb.de
Organization:
Location:
Issuer: Let's Encrypt Authority X3
Valid from: Sep 27 06:40:41 2019 GMT
Valid until: Dec 26 06:40:41 2019 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

wormex.io does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Sat, 09 Nov 2019 01:11:03 GMT
Server: Apache/2.4.25 (Debian)
Set-Cookie: __tad=1573261863.4452452; expires=Tue, 06-Nov-2029 01:11:03 GMT; Max-Age=315360000
Location: http://ww1.wormex.io/
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8

HTTP/1.1 200 OK
Date: Sat, 09 Nov 2019 01:11:04 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Vary: Accept-Encoding
Expires: Mon, 26 Jul 1997 05:00:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
X-Adblock-Key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBANnylWw2vLY4hUn9w06zQKbhKBfvjFUCsdFlb6TdQhxb9RXWXuI4t31c+o8fYOv/s8q1LGPga3DE1L/tHU4LENMCAwEAAQ==_zEBrpya1VbsuqRSB1Je78RIP2uFlTxC1vj9JC3awIQbA3Pi9Ez40bshvst3XawtQXQOa7qLSPj2arEAvS5zK3w==
Set-Cookie: tu=ba03dbbe97bcb69645edd2e334d32873; expires=Tue, 31-Dec-2019 23:00:00 GMT; Max-Age=4571336; path=/; domain=wormex.io; HttpOnly
Last-Modified: Sat, 09 Nov 2019 01:11:03 GMT
X-Cache-Miss-From: parking-774c787d8c-2hfvn
Server: NginX
Content-Encoding: gzip

+ DNS Lookup

Type Ip Target TTL
MX park-mx.above.com 3600
SOA 60
Mname ns2.above.com
Rname hostmaster.trellian.com
Serial Number 2019110901
Refresh 10800
Retry 3600
Expire 604800
Minimum TTL 0
A 103.224.182.252 3600
NS ns1.above.com 3600
NS ns2.above.com 3600

+ Whois Lookup

Domain Created:
2018-01-27
Domain Age:
1 years 9 months 12 days  
WhoIs:
 

whois lookup at whois.nic.io...
Domain Name: WORMEX.IO
Registry Domain ID: D503300000059734922-LRMS
Registrar WHOIS Server: whois.1api.net
Registrar URL: http://www.1api.net
Updated Date: 2019-01-27T22:28:53Z
Creation Date: 2018-01-27T05:33:36Z
Registry Expiry Date: 2020-01-27T05:33:36Z
Registrar Registration Expiration Date:
Registrar: 1API GmbH
Registrar IANA ID: 1387
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +49.6841***84200
Reseller:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registrant Organization: Registrant of wormex.io
Registrant State/Province: West Yorkshire
Registrant Country: GB
Name Server: NS2.ABOVE.COM
Name Server: NS1.ABOVE.COM
DNSSEC: unsigned

>>> Last update of WHOIS database: 2019-11-09T01:10:26Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Access to WHOIS information provided by Internet Computer Bureau Ltd. ("ICB") is provided to assist persons in determining the contents of a domain name registration record in the ICB registry database. The data in this record is provided by ICB for informational purposes only, and ICB does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no cir***stances will you use this data to(i) allow, enable, or otherwise support the transmission by e-mail, telephone, facsimile or other electronic means of mass, unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (ii) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or ICB or its services providers except as reasonably necessary to register domain names or modify existing registrations. UK privacy laws limit the scope of information permitted for certain public access. Therefore, concerns regarding abusive use of domain registrations in the ICB registry should be directed to either (a) the Registrar of Record as indicated in the WHOIS output, or (b) the ICB anti-abuse department at email.

All rights reserved. ICB reserves the right to modify these terms at any time. By submitting this query, you agree to abide by these policies

The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Last update was 4 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with wormex.io in any way. Only publicly available statistics data are displayed.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
wormex.io widget