Weckx.Net - Info weckx.net

weckx.net receives about 454 unique visitors and 454 (1.00 per visitor) page views per day which should earn about $1.85/day from advertising revenue. Estimated site value is $1,351.08. According to Alexa Traffic Rank weckx.net is ranked number 3,036,004 in the world and 1.0E-5% of global Internet users visit it. Site is hosted in Atlanta, Georgia, 30301, United States and links to network IP address 45.33.96.157. This server supports HTTPS and HTTP/2.

About - weckx.net


Technologies used on Website

Font Scripts
Google Font API
Web Servers
Nginx
Reverse proxies
Nginx
Programming Languages
PHP
CMS
WordPress
Blogs
WordPress
JavaScript Libraries
jQuery Migrate
jQuery
Databases
MySQL

weckx.net Profile

Title: Felipe Weckx
Last update was 126 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is weckx.net?

454 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
454
Monthly Unique Visitors:
10,896
Pages per Visit:
1.00
Daily Pageviews:
454
Alexa Rank:
3,036,004 visit alexa
Alexa Reach:
1.0E-5%   (of global internet users)
Avg. visit duration:
n/a
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:
  weckx.net
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 weckx.net?

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:
weckx.net
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:
weckx.net
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 weckx.net can earn?

Daily Revenue:
$1.85
Monthly Revenue:
$55.50
Yearly Revenue:
$675.25
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do weckx.net 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 weckx.net worth?

Website Value:
$1,351.08

+ Where is weckx.net hosted?

Server IP:
45.33.96.157
ASN:
AS63949 
ISP:
Linode, LLC 
Server Location:
Atlanta
Georgia, GA
30301
United States, US
 

Other sites hosted on 45.33.96.157

There are no other sites hosted on this IP

+ How fast does weckx.net load?

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

Page Speed (Google PageSpeed Insights) - Desktop

96
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

Max Potential First Input Delay 40 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 1.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
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.
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 0 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.0 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 1.0 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 1.0 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Eliminate render-blocking resources - Potential savings of 300 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
https://fonts.googleapis.com/css?family=Copse
1 KB230
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/css/min/crayon.min.css?ver=_2.7.2_beta
20 KB390
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/themes/classic/classic.css?ver=_2.7.2_beta
5 KB270
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/fonts/consolas.css?ver=_2.7.2_beta
1 KB230
https://blog.weckx.net/wp-content/themes/weckx-theme/css/bootstrap.min.css?ver=3.0.0
107 KB590
https://blog.weckx.net/wp-content/themes/weckx-theme/style.css?ver=1.0
2 KB230
https://blog.weckx.net/wp-includes/js/jquery/jquery.js?ver=1.12.4
95 KB590
https://blog.weckx.net/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
10 KB310
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/js/min/crayon.min.js?ver=_2.7.2_beta
22 KB390
Enable text compression - Potential savings of 214 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
https://blog.weckx.net/wp-content/themes/weckx-theme/css/bootstrap.min.css?ver=3.0.0
107 KB89 KB
https://blog.weckx.net/wp-includes/js/jquery/jquery.js?ver=1.12.4
95 KB62 KB
https://blog.weckx.net/wp-content/themes/weckx-theme/js/bootstrap.min.js?ver=3.0.0
31 KB23 KB
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/css/min/crayon.min.css?ver=_2.7.2_beta
20 KB16 KB
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/js/min/crayon.min.js?ver=_2.7.2_beta
22 KB15 KB
https://blog.weckx.net/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
10 KB6 KB
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/themes/classic/classic.css?ver=_2.7.2_beta
4 KB4 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://weckx.net/
0 ms29 ms0 KB0 KB301text/html
https://weckx.net/
30 ms218 ms27 KB143 KB200text/htmlDocument
https://fonts.googleapis.com/css?family=Copse
234 ms255 ms1 KB0 KB200text/cssStylesheet
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/css/min/crayon.min.css?ver=_2.7.2_beta
234 ms330 ms20 KB20 KB200text/cssStylesheet
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/themes/classic/classic.css?ver=_2.7.2_beta
234 ms254 ms5 KB4 KB200text/cssStylesheet
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/fonts/consolas.css?ver=_2.7.2_beta
235 ms252 ms1 KB1 KB200text/cssStylesheet
https://blog.weckx.net/wp-content/themes/weckx-theme/css/bootstrap.min.css?ver=3.0.0
235 ms299 ms107 KB107 KB200text/cssStylesheet
https://blog.weckx.net/wp-content/themes/weckx-theme/style.css?ver=1.0
235 ms322 ms2 KB1 KB200text/cssStylesheet
https://blog.weckx.net/wp-includes/js/jquery/jquery.js?ver=1.12.4
236 ms278 ms95 KB95 KB200application/javascriptScript
https://blog.weckx.net/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
236 ms332 ms10 KB10 KB200application/javascriptScript
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/js/min/crayon.min.js?ver=_2.7.2_beta
236 ms269 ms22 KB22 KB200application/javascriptScript
https://weckx.net/wp-content/uploads/2014/06/Captura-de-tela-de-2014-06-20-104921.png
236 ms253 ms4 KB4 KB200image/pngImage
https://weckx.net/wp-content/uploads/2014/02/config_tunel_firefox.png
242 ms366 ms56 KB56 KB200image/pngImage
https://blog.weckx.net/wp-content/themes/weckx-theme/js/bootstrap.min.js?ver=3.0.0
254 ms285 ms31 KB31 KB200application/javascriptScript
https://blog.weckx.net/wp-includes/js/wp-embed.min.js?ver=4.6.10
317 ms393 ms2 KB1 KB200application/javascriptScript
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/css/images/toolbar/buttons.png
374 ms390 ms3 KB2 KB200image/pngImage
https://fonts.gstatic.com/s/copse/v9/11hPGpDKz1rGb3dkFEk.woff2
394 ms399 ms27 KB26 KB200font/woff2Font
https://blog.weckx.net/wp-content/themes/weckx-theme/fonts/glyphicons-halflings-regular.woff
394 ms440 ms23 KB23 KB200application/font-woffFont
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/fonts/consolas/consolas-webfont.woff
423 ms440 ms24 KB23 KB200application/font-woffFont
Serve static assets with an efficient cache policy - 2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/fonts/consolas/consolas-webfont.woff
0 ms24 KB
https://blog.weckx.net/wp-content/themes/weckx-theme/fonts/glyphicons-halflings-regular.woff
0 ms23 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
249 ms
8 ms
282 ms
58 ms
343 ms
5 ms
359 ms
20 ms
385 ms
11 ms
396 ms
122 ms
528 ms
6 ms
534 ms
82 ms
616 ms
76 ms
692 ms
7 ms
1661 ms
13 ms
1677 ms
7 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
https://fonts.gstatic.com/s/copse/v9/11hPGpDKz1rGb3dkFEk.woff2
5 ms
https://blog.weckx.net/wp-content/themes/weckx-theme/fonts/glyphicons-halflings-regular.woff
46 ms
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/fonts/consolas/consolas-webfont.woff
17 ms
JavaScript execution time - 0.2 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
Other
299 ms3 ms1 ms
https://blog.weckx.net/wp-includes/js/jquery/jquery.js?ver=1.12.4
201 ms176 ms2 ms
https://weckx.net/
57 ms57 ms1 ms
Defer offscreen images - Potential savings of 60 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

URL
SizePotential Savings
https://weckx.net/wp-content/uploads/2014/02/config_tunel_firefox.png
56 KB56 KB
https://weckx.net/wp-content/uploads/2014/06/Captura-de-tela-de-2014-06-20-104921.png
4 KB4 KB
Remove unused CSS - Potential savings of 116 KB
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.

URL
SizePotential Savings
https://blog.weckx.net/wp-content/themes/weckx-theme/css/bootstrap.min.css?ver=3.0.0
107 KB101 KB
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/css/min/crayon.min.css?ver=_2.7.2_beta
20 KB14 KB
Avoids enormous network payloads - Total size was 460 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://blog.weckx.net/wp-content/themes/weckx-theme/css/bootstrap.min.css?ver=3.0.0
107 KB
https://blog.weckx.net/wp-includes/js/jquery/jquery.js?ver=1.12.4
95 KB
https://weckx.net/wp-content/uploads/2014/02/config_tunel_firefox.png
56 KB
https://blog.weckx.net/wp-content/themes/weckx-theme/js/bootstrap.min.js?ver=3.0.0
31 KB
https://weckx.net/
27 KB
https://fonts.gstatic.com/s/copse/v9/11hPGpDKz1rGb3dkFEk.woff2
27 KB
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/fonts/consolas/consolas-webfont.woff
24 KB
https://blog.weckx.net/wp-content/themes/weckx-theme/fonts/glyphicons-halflings-regular.woff
23 KB
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/js/min/crayon.min.js?ver=_2.7.2_beta
22 KB
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/css/min/crayon.min.css?ver=_2.7.2_beta
20 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
245 ms
Style & Layout
201 ms
Other
50 ms
Rendering
47 ms
Parse HTML & CSS
21 ms
Script Parsing & Compilation
7 ms
Serve images in next-gen formats - Potential savings of 35 KB
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.

URL
SizePotential Savings
https://weckx.net/wp-content/uploads/2014/02/config_tunel_firefox.png
56 KB35 KB
Avoid an excessive DOM size - 2,202 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
2,202
Maximum DOM Depth
14
Maximum Child Elements
75
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://weckx.net/)
0
https://weckx.net/
190
Keep request counts low and transfer sizes small - 19 requests • 460 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
19460 KB
Script
5161 KB
Stylesheet
6135 KB
Font
373 KB
Image
363 KB
Document
127 KB
Other
10 KB
Media
00 KB
Third-party
228 KB
Server response times are low (TTFB) - Root document took 190 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.

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.

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.

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.

Avoid chaining critical requests - 14 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.


Page Speed (Google PageSpeed Insights) - Mobile

68
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

Max Potential First Input Delay 170 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.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
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.
First Contentful Paint (3G) 8790 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. 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 80 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 4.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 4.7 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 4.3 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 4.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Eliminate render-blocking resources - Potential savings of 1,800 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
https://fonts.googleapis.com/css?family=Copse
1 KB780
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/css/min/crayon.min.css?ver=_2.7.2_beta
20 KB1830
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/themes/classic/classic.css?ver=_2.7.2_beta
5 KB1080
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/fonts/consolas.css?ver=_2.7.2_beta
1 KB780
https://blog.weckx.net/wp-content/themes/weckx-theme/css/bootstrap.min.css?ver=3.0.0
107 KB3030
https://blog.weckx.net/wp-content/themes/weckx-theme/style.css?ver=1.0
2 KB930
https://blog.weckx.net/wp-includes/js/jquery/jquery.js?ver=1.12.4
95 KB2880
https://blog.weckx.net/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
10 KB1380
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/js/min/crayon.min.js?ver=_2.7.2_beta
22 KB1830
Enable text compression - Potential savings of 214 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
https://blog.weckx.net/wp-content/themes/weckx-theme/css/bootstrap.min.css?ver=3.0.0
107 KB89 KB
https://blog.weckx.net/wp-includes/js/jquery/jquery.js?ver=1.12.4
95 KB62 KB
https://blog.weckx.net/wp-content/themes/weckx-theme/js/bootstrap.min.js?ver=3.0.0
31 KB23 KB
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/css/min/crayon.min.css?ver=_2.7.2_beta
20 KB16 KB
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/js/min/crayon.min.js?ver=_2.7.2_beta
22 KB15 KB
https://blog.weckx.net/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
10 KB6 KB
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/themes/classic/classic.css?ver=_2.7.2_beta
4 KB4 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://weckx.net/
0 ms132 ms0 KB0 KB301text/html
https://weckx.net/
133 ms380 ms27 KB142 KB200text/htmlDocument
https://fonts.googleapis.com/css?family=Copse
395 ms415 ms1 KB0 KB200text/cssStylesheet
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/css/min/crayon.min.css?ver=_2.7.2_beta
395 ms573 ms20 KB20 KB200text/cssStylesheet
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/themes/classic/classic.css?ver=_2.7.2_beta
396 ms562 ms5 KB4 KB200text/cssStylesheet
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/fonts/consolas.css?ver=_2.7.2_beta
396 ms549 ms1 KB1 KB200text/cssStylesheet
https://blog.weckx.net/wp-content/themes/weckx-theme/css/bootstrap.min.css?ver=3.0.0
397 ms617 ms107 KB107 KB200text/cssStylesheet
https://blog.weckx.net/wp-content/themes/weckx-theme/style.css?ver=1.0
397 ms539 ms2 KB1 KB200text/cssStylesheet
https://blog.weckx.net/wp-includes/js/jquery/jquery.js?ver=1.12.4
397 ms602 ms95 KB95 KB200application/javascriptScript
https://blog.weckx.net/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
397 ms572 ms10 KB10 KB200application/javascriptScript
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/js/min/crayon.min.js?ver=_2.7.2_beta
398 ms572 ms22 KB22 KB200application/javascriptScript
https://weckx.net/wp-content/uploads/2014/06/Captura-de-tela-de-2014-06-20-104921.png
398 ms479 ms4 KB4 KB200image/pngImage
https://weckx.net/wp-content/uploads/2014/02/config_tunel_firefox.png
404 ms494 ms56 KB56 KB200image/pngImage
https://blog.weckx.net/wp-content/themes/weckx-theme/js/bootstrap.min.js?ver=3.0.0
481 ms598 ms31 KB31 KB200application/javascriptScript
https://blog.weckx.net/wp-includes/js/wp-embed.min.js?ver=4.6.10
495 ms596 ms2 KB1 KB200application/javascriptScript
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/css/images/toolbar/buttons.png
672 ms689 ms3 KB2 KB200image/pngImage
https://fonts.gstatic.com/s/copse/v9/11hPGpDKz1rGb3dkFEmDUq-B.woff2
697 ms702 ms20 KB19 KB200font/woff2Font
https://blog.weckx.net/wp-content/themes/weckx-theme/fonts/glyphicons-halflings-regular.woff
697 ms752 ms23 KB23 KB200application/font-woffFont
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/fonts/consolas/consolas-webfont.woff
730 ms759 ms24 KB23 KB200application/font-woffFont
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/css/images/toolbar/buttons@2x.png
939 ms957 ms3 KB3 KB200image/pngImage
Serve static assets with an efficient cache policy - 2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/fonts/consolas/consolas-webfont.woff
0 ms24 KB
https://blog.weckx.net/wp-content/themes/weckx-theme/fonts/glyphicons-halflings-regular.woff
0 ms23 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
402 ms
8 ms
436 ms
45 ms
638 ms
6 ms
644 ms
24 ms
673 ms
13 ms
687 ms
145 ms
844 ms
93 ms
938 ms
82 ms
1020 ms
8 ms
1033 ms
5 ms
1987 ms
15 ms
2002 ms
7 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
https://fonts.gstatic.com/s/copse/v9/11hPGpDKz1rGb3dkFEmDUq-B.woff2
5 ms
https://blog.weckx.net/wp-content/themes/weckx-theme/fonts/glyphicons-halflings-regular.woff
55 ms
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/fonts/consolas/consolas-webfont.woff
29 ms
JavaScript execution time - 1.0 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
Other
1346 ms15 ms4 ms
https://blog.weckx.net/wp-includes/js/jquery/jquery.js?ver=1.12.4
872 ms765 ms8 ms
https://weckx.net/
176 ms174 ms3 ms
Defer offscreen images - Potential savings of 63 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

URL
SizePotential Savings
https://weckx.net/wp-content/uploads/2014/02/config_tunel_firefox.png
56 KB56 KB
https://weckx.net/wp-content/uploads/2014/06/Captura-de-tela-de-2014-06-20-104921.png
4 KB4 KB
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/css/images/toolbar/buttons@2x.png
3 KB3 KB
Remove unused CSS - Potential savings of 117 KB
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.

URL
SizePotential Savings
https://blog.weckx.net/wp-content/themes/weckx-theme/css/bootstrap.min.css?ver=3.0.0
107 KB102 KB
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/css/min/crayon.min.css?ver=_2.7.2_beta
20 KB15 KB
Avoids enormous network payloads - Total size was 456 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://blog.weckx.net/wp-content/themes/weckx-theme/css/bootstrap.min.css?ver=3.0.0
107 KB
https://blog.weckx.net/wp-includes/js/jquery/jquery.js?ver=1.12.4
95 KB
https://weckx.net/wp-content/uploads/2014/02/config_tunel_firefox.png
56 KB
https://blog.weckx.net/wp-content/themes/weckx-theme/js/bootstrap.min.js?ver=3.0.0
31 KB
https://weckx.net/
27 KB
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/fonts/consolas/consolas-webfont.woff
24 KB
https://blog.weckx.net/wp-content/themes/weckx-theme/fonts/glyphicons-halflings-regular.woff
23 KB
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/js/min/crayon.min.js?ver=_2.7.2_beta
22 KB
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/css/min/crayon.min.css?ver=_2.7.2_beta
20 KB
https://fonts.gstatic.com/s/copse/v9/11hPGpDKz1rGb3dkFEmDUq-B.woff2
20 KB
Minimize main-thread work - 2.4 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
985 ms
Style & Layout
874 ms
Other
233 ms
Rendering
222 ms
Parse HTML & CSS
95 ms
Script Parsing & Compilation
31 ms
Garbage Collection
2 ms
Serve images in next-gen formats - Potential savings of 35 KB
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.

URL
SizePotential Savings
https://weckx.net/wp-content/uploads/2014/02/config_tunel_firefox.png
56 KB35 KB
Avoid an excessive DOM size - 2,184 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
2,184
Maximum DOM Depth
14
Maximum Child Elements
75
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://weckx.net/)
0
https://weckx.net/
630
Keep request counts low and transfer sizes small - 20 requests • 456 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
20456 KB
Script
5161 KB
Stylesheet
6135 KB
Image
467 KB
Font
366 KB
Document
127 KB
Other
10 KB
Media
00 KB
Third-party
221 KB
Server response times are low (TTFB) - Root document took 250 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.

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.

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.

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.

Avoid chaining critical requests - 14 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.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

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

Your page has 3 blocking script resources and 6 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:

https://blog.weckx.net/wp-includes/js/jquery/jquery.js?ver=1.12.4
https://blog.weckx.net/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/js/min/crayon.min.js?ver=_2.7.2_beta
Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Copse
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/css/min/crayon.min.css?ver=_2.7.2_beta
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/themes/classic/classic.css?ver=_2.7.2_beta
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/fonts/consolas.css?ver=_2.7.2_beta
https://blog.weckx.net/wp-content/themes/weckx-theme/css/bootstrap.min.css?ver=3.0.0
https://blog.weckx.net/wp-content/themes/weckx-theme/style.css?ver=1.0

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 222.2KiB (73% reduction).

Compressing https://blog.weckx.net/wp-content/themes/weckx-theme/css/bootstrap.min.css?ver=3.0.0 could save 89.2KiB (83% reduction).
Compressing https://blog.weckx.net/wp-includes/js/jquery/jquery.js?ver=1.12.4 could save 61.9KiB (65% reduction).
Compressing https://blog.weckx.net/wp-content/themes/weckx-theme/js/bootstrap.min.js?ver=3.0.0 could save 22.7KiB (73% reduction).
Compressing https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/css/min/crayon.min.css?ver=_2.7.2_beta could save 15.8KiB (80% reduction).
Compressing https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/js/min/crayon.min.js?ver=_2.7.2_beta could save 15.2KiB (***% reduction).
Compressing https://blog.weckx.net/wp-includes/js/wp-emoji-release.min.js?ver=4.6.10 could save 6.3KiB (61% reduction).
Compressing https://blog.weckx.net/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1 could save 5.9KiB (60% reduction).
Compressing https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/themes/classic/classic.css?ver=_2.7.2_beta could save 3.6KiB (83% reduction).
Compressing https://blog.weckx.net/wp-content/themes/weckx-theme/style.css?ver=1.0 could save 662B (55% reduction).
Compressing https://blog.weckx.net/wp-includes/js/wp-embed.min.js?ver=4.6.10 could save 653B (47% reduction).
Compressing https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/fonts/consolas.css?ver=_2.7.2_beta could save 318B (56% reduction).

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 <div class="crayon-button…crayon-pressed"></div> and 8 others are close to other tap targets.
The tap target <div class="crayon-button…n-plain-button"></div> and 34 others are close to other tap targets.
The tap target <textarea class="crayon-plain print-no">MD5 felipe0111…ab3b58405ed4a8</textarea> is close to 1 other tap targets.
The tap target <a href="https://blog.w…/autenticacao/">autenticação</a> and 16 others are close to other tap targets.
The tap target <a href="https://blog.w…-php/#comments">2 comentários</a> and 9 others are close to other tap targets.
The tap target <a href="http://php.net/json">JSON</a> and 5 others are close to other tap targets.

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:

https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/fonts/consolas/consolas-webfont.ttf (expiration not specified)
https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/fonts/consolas/consolas-webfont.woff (expiration not specified)
https://blog.weckx.net/wp-content/themes/weckx-theme/fonts/glyphicons-halflings-regular.ttf (expiration not specified)
https://blog.weckx.net/wp-content/themes/weckx-theme/fonts/glyphicons-halflings-regular.woff (expiration not specified)

Optimize images

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

Optimize the following images to reduce their size by 17.8KiB (28% reduction).

Compressing https://weckx.net/wp-content/uploads/2014/02/config_tunel_firefox.png could save 14.8KiB (27% reduction).
Compressing https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/css/images/toolbar/buttons.png could save 1KiB (48% reduction).
Compressing https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/css/images/toolbar/buttons@2x.png could save 1KiB (33% reduction).
Compressing https://weckx.net/wp-content/uploads/2014/06/Captura-de-tela-de-2014-06-20-104921.png could save 974B (24% reduction).

Reduce server response time

In our test, your server responded in 0.21 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

Minify CSS

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

Minify CSS for the following resources to reduce their size by 967B (18% reduction).

Minifying https://blog.weckx.net/wp-content/themes/weckx-theme/style.css?ver=1.0 could save 488B (42% reduction).
Minifying https://blog.weckx.net/wp-content/plugins/crayon-syntax-highlighter/themes/classic/classic.css?ver=_2.7.2_beta could save 479B (11% 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.
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.
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 weckx.net use compression?

weckx.net use gzip compression.
Original size: 142.7 KB
Compressed size: 26.69 KB
File reduced by: 116.01 KB (81%)

+ 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

weckx.net supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: weckx.net
Organization:
Location:
Issuer: Let's Encrypt Authority X3
Valid from: Nov 19 10:35:20 2019 GMT
Valid until: Feb 17 10:35:20 2020 GMT
Authority: Is not a CA
Keysize:
Common Name: Let's Encrypt Authority X3
Organization: Let's Encrypt
Location: US
Issuer: DST Root CA X3
Valid from: Mar 17 16:40:46 2016 GMT
Valid until: Mar 17 16:40:46 2021 GMT
Authority: Is a CA
Keysize: 2048 Bits

+ Verify HTTP/2 Support

weckx.net supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: nginx/1.10.3
Date: Sat, 23 Nov 2019 18:30:02 GMT
Content-Type: text/html
Content-Length: 185
Connection: keep-alive
Location: https://weckx.net/

HTTP/2 200 
server: nginx/1.10.3
date: Sat, 23 Nov 2019 18:30:03 GMT
content-type: text/html; charset=UTF-8
x-powered-by: PHP/7.2.12
set-cookie: pll_language=pt; expires=Sun, 22-Nov-2020 18:30:03 GMT; Max-Age=31536000; path=/
link: <https://blog.weckx.net/wp-json/>; rel="https://api.w.org/"
strict-transport-security: max-age=15768000
content-encoding: gzip

+ DNS Lookup

Currently Not Available

+ Whois Lookup

Domain Created:
2008-01-09
Domain Age:
11 years 10 months 14 days  
WhoIs:
 

whois lookup at whois.dyndns.com...
Domain Name: WECKX.NET
Registry Domain ID: 13754***763_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.dyndns.com
Registrar URL: http://www.oracle.com
Updated Date: 2019-01-04T11:33:18Z
Creation Date: 2008-01-09T18:02:11Z
Registrar Registration Expiration Date: 2021-01-09T18:02:11Z
Registrar: Oracle America, Inc.
Registrar IANA ID: 1040
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1 (603) 296-1595
Domain Status: clientDeleteProhibited
Domain Status: clientTransferProhibited
Domain Status: clientUpdateProhibited
Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Felipe Weckx
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province:
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: BR
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: https://account.dyn.com/dns/domain-registration/contact/weckx.net/registrant/
Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: https://account.dyn.com/dns/domain-registration/contact/weckx.net/admin/
Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: https://account.dyn.com/dns/domain-registration/contact/weckx.net/tech/
Name Server: NS1.LINODE.COM
Name Server: NS2.LINODE.COM
Name Server: NS3.LINODE.COM
Name Server: NS4.LINODE.COM
Name Server: NS5.LINODE.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2019-11-23T18:22:36Z <<<
whois lookup at whois.crsnic.net...
Domain Name: WECKX.NET
Registry Domain ID: 13754***763_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.dyndns.com
Registrar URL: http://www.oracle.com
Updated Date: 2019-01-04T11:33:18Z
Creation Date: 2008-01-09T18:02:11Z
Registry Expiry Date: 2021-01-09T18:02:11Z
Registrar: Oracle America, Inc.
Registrar IANA ID: 1040
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1 (603) 296-1595
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Name Server: NS1.LINODE.COM
Name Server: NS2.LINODE.COM
Name Server: NS3.LINODE.COM
Name Server: NS4.LINODE.COM
Name Server: NS5.LINODE.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2019-11-23T18:30:10Z <<<

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

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no cir***stances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.
Last update was 126 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with weckx.net in any way. Only publicly available statistics data are displayed.
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

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!
weckx.net widget