hector.network Hector.network

   
Hector Network

Domain Summary

What is the traffic rank for Hector.network?

• Hector.network ranks #3,833,730 globally on HypeStat.

What percent of global Internet users visit Hector.network?

• 1.16E-5% of global Internet users visit Hector.network

How many people visit Hector.network each day?

• Hector.network receives approximately 572 visitors and 903 page impressions per day.

Which countries does Hector.network receive most of its visitors from?

• Hector.network is mostly visited by people located in Viet Nam,Turkey,Indonesia.

How much Hector.network can earn?

• Hector.network should earn about $3.05/day from advertising revenue.

What is Hector.network estimated value?

• Estimated value of Hector.network is $2,744.49.

What IP addresses does Hector.network resolve to?

• Hector.network resolves to the IP addresses 2606:4700:20::ac43:49b5, 172.67.73.181.

Where are Hector.network servers located in?

• Hector.network has servers located in United States.

hector.network Profile

Title:Hector Network
Description:    as it was announced, the liquidation committee has prepared answers to frequently asked questions delivered by moderators who collected them in various chat groups, and they are available at https://ow.ly/e89450pnbo2. questions that may have been missed or may emerge till the redemption conclusion can be sent on the following email address questions@hector.network and the answers will be added to the faqs update(s). we would like to take this opportunity to remind you of the importance of relying on communication from official sources only. this ensures that you receive accurate information and avoids any potential misinformation that may be circulating. thank you for your cooperation and understanding. liquidation committee last updated 18 aug 2023   can the approximate time frame for the individual tasks or group of tasks be provided? the liquidation process involves several tasks, each with its own estimated time frame. here are the approximate time frames for the key tasks: liquidation of the corporate entities: the liquidation process for the corporate entities is expected to take 6-8 weeks because it involves posting public notices to creditors and disposition of any assets and liabilities. however, this process will be carefully timed to coincide with the hector network treasury liquidation. it is important to ensure that both the corporate entities and the hector network treasury are liquidated simultaneously to prevent hector network from losing the ability to interact with off-chain service providers once the entities are liquidated. this process will be overseen by a third-party liquidator to ensure its transparency and is critical in ensuring that all assets of hector network are distributed to the tokenholders. time period for tokenholders to claim their corresponding share of the hector network’s treasury: tokenholders will have a 3-month registration window for their wallets. after the registration window, they will be given an additional 2 months to claim their share of the treasury. this extended period has been designed to allow all tokenholders, including those who may not actively follow the situation, sufficient time to make their claims. the goal is to ensure that nobody is disadvantaged during the redemption process. notice period to remove tokens from the fantom and casper validators: to facilitate the redemption process, there is a notice period of 3 months to remove tokens from the fantom and casper validators. notice period for bitmart and bitrue centralised exchanges: bitmart and bitrue centralised exchanges require a 2-month notice to remove tokens. fulfilment of existing contractual obligations: fulfilling existing contractual obligations is expected to take between 1 to 3 months. the exact time frame may vary depending on the complexity of the contracts and agreements involved. these obligations involve, for example, the termination and offboarding of external developers responsible for the development of the technical infrastructure with various termination notice periods. audit of the redemption contracts by certik and hacken: the estimated time for the audit of the redemption contracts by certik and hacken is yet to be determined but we expect it to take approximately 2 to 3 months. this audit is a crucial step in ensuring the security and accuracy of the redemption process. winding down of infrastructure, planning, architecture, development and deployment of redemption contracts and interface: the estimated time for winding down all infrastructure, including emissions plan, farming, liquidity pools, development and deployment of the redemption contracts and interface dapp, is still to be determined, but we currently estimate it to take 4 to 5 months which may be subject to change. these tasks involve meticulous planning and *** with multiple dependencies that need to be effectively managed. this is crucial in guaranteeing a seamless transition and ensuring the secure facilitation of redemption procedures for all variants of the hec token and their respective value compositions. together with the abovementioned audit, this step is intended to create confidence that the redemption mechanism cannot be abused. it is important to note that not all tasks can be completed in parallel, as certain tasks are sequential and depend on the completion of others. the liquidation committee is diligently working on the redemption process, and some timelines are subject to change due to unforeseen circumstances.   who, from the hector network team will be included in the liquidation process and with what role? the liquidation process will be overseen and run by the liquidation committee, which consists of: legal counsel: sparring smart contract auditors: certik and hacken bvi and rmi liquidators: to be assigned by the legal counsel financial statements and asset liquidation: head of finance infrastructure closure: head of development for more information, you can visit: https://t.me/hectornetworkann/1553.   what will happen with the treasury? will it stay on fantom or be transferred to the other chain and what tokens will be used for the redemption? as part of the redemption process, the tokens held in the treasury are being swapped for usdc and usdt on ethereum. the proposed redemption will be in one of these stablecoins issued on ethereum. currently, 60% of the treasury assets are held in stablecoins and this amount will continue to steadily increase in the coming weeks as tokens are unlocked as well as swapped into stablecoins as the market liquidity permits and 24% are in ethereum. 91% of assets are held in the top 5 tokens and stablecoins. the assets are distributed across different chains as follows: 85% on ethereum, 7% on fantom, 4% on binance smart chain, and 4% on bitcoin and other chains. transparency on the tokens held in the treasury is still provided through the dashboard accessible at the url: dashboard — hector network note: this question has been updated in redemption faqs update #1.   what are the total approximate expenses and payment obligations needed to be settled prior to the redemption? there are approximately $1.2 million in payment obligations arising from partnership agreements, software development, legal and operating expenses, and other contractual obligations. this amount also includes the estimated cost of disposition and completion of the token redemption. over 50% of these obligations stem from agreements dated in 2022 and q1 2023 but must be honoured to avoid disputes.   what $usd value can i expect to get for 1 hec? the value tokenholders will receive for 1 hec in usd will depend on the token value of the treasury assets at the time of redemption, after deducting all contractual, statutory, legal obligations, and liquidation costs that must be fully settled. the dashboard of the treasury assets is still accessible at the url https://beta.hector.network/ and provides transparency on the tokens held in the treasury.   what token(s) will people receive in the redemption? redemption is anticipated to be provided in the form of usdt or usdc on the ethereum blockchain.   what will i need for claiming funds in the redemption? tokenholders will need to keep their hec tokens after the snapshot has been taken in order to claim the redemption. the redemption process will involve a multi-step approach. in the first phase, tokenholders will be required to register their wallets with various versions of their hec tokens, including fntf. once the registration period is concluded, and their wallets are whitelisted into the redemption contract, tokenholders will then need to sign a transaction to send their tokens to the redemption contract. as a result, they will receive the redemption value in the form of usdt or usdc tokens on the ethereum blockchain.   do i have to keep my hec after the snapshot has been taken in order to claim? yes. for more details, please refer to the answer provided to a previous question.    what should i do with my staked, wrapped hec and hec deposited in the farms? it is essential to follow the instructions announced by the liquidation committee on the official channels. the liquidation committee has already communicated and will continue to provide guidance on the necessary actions to be taken. to check announcements posted so far, please visit one of the following channels: https://t.me/hectornetworkann https://discord.gg/hector https://twitter.com/hector_network future information will also be posted on the website starting next week.   will unclaimed farm and staking rewards participate in the redemption? for any hec tokens that have been locked before the cut-off block number that was announced, a comprehensive plan is currently being developed to cater to all redemption situations that fall within the specified cut-off block number. this is a complex aspect of the redemption system, and further information will be provided after the process finalisation.   what will happen with the usdc and tor in the farms? all liquidity will be removed.   how much time will users have for claiming in the redemption and what will happen with unclaimed funds?  as described in the answers to previous questions, the redemption process will involve a multi-step approach. in the first phase, tokenholders will have a 3-month window to register their wallets. once the registration period is concluded, and wallets are whitelisted into the redemption contract, tokenholders with whitelisted wallets will have an additional 2 months to claim their share of the treasury. any funds that go unclaimed during the registration phase will be proportionally redistributed among the tokenholders with whitelisted wallets so that no funds are left over at the end of the redemption process.    if my $hec tokens were stored on a ledger (or any other offline hardware wallet) at the time of the snapshot, were they still considered for the snapshot? if $hec tokens were stored on a ledger at the time of the snapshot, they were still considered for the snapshot. the snapshot is a record of a blockchain block number, so tokens held by tokenholders will be included in that block, regardless of the wallet they were stored in. this does not apply to exchange accounts.   the liquidation is only talking about treasury, but what are they going to do with the code and documentation (that's hn ip)? will that be sold (to increase the payout to holders), made open to holders or will the remaining liquidation team keep that for themself?  the future of hector network's intellectual property (ip), is currently being considered as part of the liquidation process. the completed ip is undergoing review and valuation. additionally, third-party auctioneers have been contacted to explore the potential sale of the intellectual property. the aim of this process is to return as much value as possible to the tokenholders. at this stage, no definite material resale value for the ip can be confirmed, and other options for auctioning the intellectual property are being explored. the handling of the ip will be determined based on the outcomes of these evaluations and auctioning efforts. as more information becomes available, updates will be provided through the official channels. what will happen to my loans currently active in the hector institute? all active loans in the hector institute should be settled, and assets withdrawn prior to the end of the redemption registration window. please be aware that failure to withdraw related tokens in a timely manner may result in the loss of your assets. for more information, please visit: https://t.me/hectornetworkann/1560   was my ownership of wshec, shec tokens taken into consideration during the snapshot for further use? yes   do i need to unwrap the current tokens that i am holding prior to the redemption?at this moment, tokenholders are advised to keep their current tokens as they are until the release of further instructions posted on the official channels. once the redemption process mechanism has been designed, verified, and audited, the liquidation committee will provide guidance on the necessary actions to be taken.   following on from the above question, what is the process of selling my wrapped tokens? wshec and hec tokens can be swapped on a decentralised exchange such as spookyswap (https://spooky.fi/#/swap). please bear in mind that as part of the hector network liquidation, tokenholders of hec token and its variants acquired before the snapshot will be able to participate in the redemption and claim a part of the hector network treasury. more information about redemption requirements can be found in the answers provided to questions 7, 8, and 9. at this moment, tokenholders are advised to keep their current tokens as they are until the release of further instructions posted on the official channels. once the redemption process mechanism has been designed, verified, and audited, the liquidation committee will provide guidance on the necessary actions to be taken.   i've just now seen the situation with hec. i still have some hec on my ftm wallet. i'm not able to swap hec to usdc on your site. is there still a way to swap it? as part of the liquidation process the swap functionality on the dapp was disabled as the project is in the process of winding down. hec tokens can be swapped on a decentralised exchange such as spookyswap (https://spooky.fi/#/swap). please bear in mind that as part of the hector network liquidation, tokenholders of hec token and its variants acquired before the snapshot will be able to participate in the redemption and claim a part of the hector network treasury. more information about redemption requirements can be found in the answers provided to questions 7, 8, and 9. at this moment, tokenholders are advised to keep their current tokens as they are until the release of further instructions posted on the official channels. once the redemption process mechanism has been designed, verified, and audited, the liquidation committee will provide guidance on the necessary actions to be taken.   as the current emission plan is not due to unlock for the next 90 days, what should i do with $hec? more information about redemption requirements can be found in the answers provided to questions 7, 8, and 9. at this moment, tokenholders are advised to keep their current tokens as they are until the release of further instructions posted on the official channels. once the redemption process mechanism has been designed, verified, and audited, the liquidation committee will provide guidance on the necessary actions to be taken.   as hec-usdc and hec-tor farms have stopped emitting, when will the liquidity pool locked for 3 years unlock? the liquidity pool will unlock before the redemption period starts.   i have shec (binance chain) stored on my ledger. how do i withdraw my assets if the https://beta.hector.network/ site does not allow me to unstake hec and withdraw? shec was never available on the binance chain. please check the version of the hec token you possess and verify the platform where you have deposited it. it's essential to ensure that you are using the correct version of hec and have it deposited on the appropriate blockchain to avoid any potential issues with withdrawing.   hello, i'm sorry hector had to close down. i nft locked my tokens over 6 months ago and i'm wondering what i need to do to be included in the liquidation. the time lock is over and i could move them back to my wallet. i also have accrued about 45 or 50 more hec from that but i have never claimed it. i just figured i would let it sit there until i wanted to unlock and claim them. at this moment, tokenholders are advised to keep their current tokens as they are until the release of further instructions posted on the official channels. once the redemption process mechanism has been designed, verified, and audited, the liquidation committee will provide guidance on the necessary actions to be taken. also, please refer to the answers provided to questions 9. and 10.   what is the next step for token holders to start the redemption process? at this moment, the most important thing is to stay updated and follow instructions from the announcements posted only on the official channels to avoid misinformation. information about the redemption process can be found in the answers to previously answered questions, and once the redemption process mechanism has been designed, verified, and audited, the liquidation committee will provide guidance on the necessary actions to be taken.   my brother has his money in tor / usdc / dai farm, what would he need to do to get that out? crvlp tokens created from tor / usdc / dai and deposited into the tor / usdc / dai farm at https://app.hector.network/farm can be withdrawn from the farm as tor or dai or usdc. please bear in mind that the tor redemption process is still under review, and further information will be provided after the process is completed.   i apologise for having to contact via this method however all other forms of communication with the company have been disconnected by the steering committee. as have some other important holder owned information channels such a medium which held a lot of the legal information regarding the governance of the company.however, the reason for my email is as follows.i would like to ask when and where we will be able to redeem our tor from the treasury. for your reference, i have included some statements made by employees at the time in the official hector network discord, as well as statements from the company on its official methods of communication such as snapshot and its cmc page.i have also included a saved copy of hip 16 direct from snapshot (snapshot) where it states the following. attached documents: tor backing cmc.pdf tor backing.jpg tor hip.pdf as of july 17, 2023, at 1600 utc time, hector network officially entered into liquidation mode with a majority vote (83.3%) from the hector network community  https://t.me/hectornetworkann/1552). as a result, all operations of hector network have ceased to exist and are currently undergoing a shutdown process. as part of the liquidation, all social media channels owned by hector network will also be shut down at the conclusion of the liquidation process. due to the lack of personnel required to manage all social media channels created prior to the liquidation period, and to ensure efficient and effective communication with all parties involved during the liquidation process, the following measures have been implemented: a. social media channels that were more frequently used have been kept in announcement mode, where all important liquidation updates will be communicated by the liquidation committee.  b. for any questions or clarifications related to the redemption process, the email address questions@hector.network has been established and announced to the community.  26.2. regarding the tor token, since its launch, several changes have been made to the tor mechanism, all of which have been announced and communicated. for detailed information about the minting, redeeming, and backing of tor, please refer to the announcements posted on june 1st, 2022 (https://discord.com/channels/902514779690790932/903000513988136990/981640143104540742), september 1st, 2022 (https://discord.com/channels/902514779690790932/903000513988136990/1014912533737512991) and september 22nd (https://twitter.com/hector_network/status/1572964075541258246?s=20). the tor redemption process is still under review, and further information will be provided after the process is completed.   there hasn't been any clear communication around how the liquidation and redemption process will impact tor? was this not an asset supported by the hector treasury as well? shouldn't those of us who were holding tor along with hec be entitled to treasury assets accordingly? please refer to the answer provided to a previous question.   what should i do with my current tor tokens? more information will be provided in the future updates regarding tor tokens. the tor redemption process is still under review, and further information will be provided after the process is completed.   i would glad to know about how will be managed oikos profit agreement? there is no profit agreement as the game was in pre-production at the time of the liquidation vote and no separate legal entity was formed.   please note that the information provided in this faq is subject to change and will be further detailed in the liquidation process. stay tuned for official updates and announcements through hector network’s official channels. questions submitted to questions@hector.network will be updated here and not answered directly via email.
Category:Finance / Investing
Edit Site Info

What technologies does hector.network use?

These are the technologies used at hector.network. hector.network has a total of 12 technologies installed in 11 different categories.
CDN
CloudFlare CloudFlare
Page builders
Elementor Elementor
Security
HSTS HSTS
JavaScript Libraries
jQuery jQuery
jQuery Migrate jQuery Migrate
Programming Languages
PHP PHP
Performance
Priority Hints Priority Hints
WordPress plugins
SVG Support SVG Support
Slider Revolution Slider Revolution
WP Rocket WP Rocket
Caching
WP Rocket WP Rocket
CMS
WordPress WordPress
Blogs
WordPress WordPress
Databases
MySQL MySQL

hector.network Traffic Analysis

Hector.network is ranked #3,833,730 in the world. This website is viewed by an estimated 572 visitors daily, generating a total of 0.9K pageviews. This equates to about 17.3K monthly visitors.
Daily Visitors572
Monthly Visits17.3K
Pages per Visit1.58
Visit duration01:35
Bounce Rate41.28%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
572
Monthly Visits:
17,332
Pages per Visit:
1.58
Daily Pageviews:
903
Avg. visit duration:
01:35
Bounce rate:
41.28%
Global Reach:
1.16E-5%
Monthly Visits (SEMrush):
5,747
Monthly Unique Visitors (SEMrush):
4,598
Monthly Visits (SimilarWeb):
17,322
HypeRank:
3,833,730
SEMrush Rank:
3,475,152
SimilarWeb Rank:
2,352,548
*All traffic values are estimates only.

Traffic sources

Direct:
87.63%
Referral:
12.37%
Search:
0%
Social:
0%
Paid:
0%

Desktop vs Mobile

Desktop:
58.10%
Mobile:
41.90%

Total Visits Last 3 Months

22.6K
JAN
17.3K
FEB
17.3K
MAR

Visitors by country

Country
Users%
 
Viet Nam 5.43%
 
Turkey 5.32%
 
Indonesia 4.58%
 
United States 4.15%
 
Spain 4.08%

Which sites are competitors to hector.network?

Websites similar to hector.network are sites similar on user interests and browsing behavior. Users can discover new websites that are similar to the ones they already enjoy or find useful.
Last update was 240 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with hector.network in any way. Only publicly available statistics data are displayed.

  ▼

SEMrush is a complete on line advertising and marketing platform that gives a extensive variety of gear and functions to help companies and entrepreneurs in enhancing their on line visibility and optimizing their virtual advertising and marketing strategies.
SemRushSemRush
Domain:
  hector.network
Rank:
(Rank based on keywords, cost and organic traffic)
  3,475,152
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  27
Organic Traffic:
(Number of visitors coming from top 20 search results)
  89
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Full SEMrush Report >>

Revenue report ▼

Google.com would generate approximately $3.1 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $91.5 and annual gross revenue of approximately $1.1K. Based on these figures, the site's net worth is estimated at around $2.7K.

How much would hector.network make?

Daily Revenue:
$3.05
Monthly Revenue:
$91.50
Yearly Revenue:
$1,113.25
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 37$0.18
 
Viet Nam 49$0.02
 
Spain 37$0.02
 
Turkey 48$0.01
 
Indonesia 41$0.00

Loss of money due to Adblock?

Daily Revenue Loss:
$0.04
Monthly Revenue Loss:
$1.20
Yearly Revenue Loss:
$14.65
Daily Pageviews Blocked:
43
Monthly Pageviews Blocked:
1,292
Yearly Pageviews Blocked:
15,725

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 7$0.03
 
Spain 7$0.00
 
Indonesia 24$0.00
 
Viet Nam 2$0.00
 
Turkey 3$0.00

How much is hector.network worth?

Website Value:
$2.7K

Ad Experience Report ▼

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

Mobile summary

Root domain:
hector.network
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

Desktop summary

Root domain:
hector.network
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 ▼

Summary of the abusive experience rating of a website.
Root domain:
hector.network
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

Where is hector.network hosted? ▼

Hector.network may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
2606:4700:20::ac43:49b5, 172.67.73.181
ASN:
AS13335 
ISP:
Cloudflare Inc 
Server Location:

United States, US
 

Other sites hosted on 172.67.73.181

How fast does hector.network load? ▼

The average loading time of hector.network is 163 ms. The Desktop speed index is 94 and mobile speed index is 37.
Average Load Time:
163 ms

Page Speed (Google PageSpeed Insights) - Desktop

94
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW 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.

Cumulative Layout Shift (CLS)43ms 28% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 28% 16% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 16% 55% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 55%
Time To First Byte (TTFB)1.2s 61% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 61% 32% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 32% 5% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 5%
First Contentful Paint (FCP)2.1s 66% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 66% 21% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 21% 12% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 12%
First Input Delay (FID)1ms 100% of loads for this page have a fast (<100ms) First Input Delay (FID) 100% 0% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)38ms 98% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 98% 0% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)2.2s 82% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 82% 12% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 12% 4% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 4%

Origin Data

All pages served from this origin have an SLOW 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.

Cumulative Layout Shift (CLS)43ms 28% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 28% 16% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 16% 55% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 55%
Time To First Byte (TTFB)1.2s 61% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 61% 32% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 32% 5% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 5%
First Contentful Paint (FCP)2.2s 66% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 66% 21% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 21% 12% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 12%
First Input Delay (FID)1ms 100% of loads for this page have a fast (<100ms) First Input Delay (FID) 100% 0% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)39ms 98% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 98% 0% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)2.2s 82% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 82% 12% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 12% 4% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 4%

Lab Data

First Contentful Paint 1.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
Speed Index 1.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Largest Contentful Paint 1.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Time to Interactive 1.1 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Timing budget  
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more about performance budgets
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Preconnect to required origins  
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
Largest Contentful Paint image was not lazily loaded  
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
First Meaningful Paint 1.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric

Page Speed (Google PageSpeed Insights) - Mobile

37
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE 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.

Cumulative Layout Shift (CLS)2ms 28% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 75% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 24% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 24%
Time To First Byte (TTFB)1.5s 61% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 41% 39% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 39% 18% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 18%
First Contentful Paint (FCP)2.5s 66% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 60% 22% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 22% 16% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 16%
First Input Delay (FID)10ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 98% 1% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)121ms 98% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 88% 7% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 7% 3% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 3%
Largest Contentful Paint (LCP)2.6s 82% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 76% 14% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 14% 9% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 9%

Origin Data

All pages served from this origin have an AVERAGE 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.

Cumulative Layout Shift (CLS)2ms 76% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 76% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 23% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 23%
Time To First Byte (TTFB)1.5s 42% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 42% 38% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 38% 18% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 18%
First Contentful Paint (FCP)2.5s 61% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 61% 21% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 21% 16% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 16%
First Input Delay (FID)10ms 100% of loads for this page have a fast (<100ms) First Input Delay (FID) 98% 1% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)121ms 89% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 89% 7% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 7% 2% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 2%
Largest Contentful Paint (LCP)2.6s 76% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 76% 14% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 14% 9% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 9%

Lab Data

Largest Contentful Paint image was not lazily loaded  
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Largest Contentful Paint 4.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Preconnect to required origins  
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
First Meaningful Paint 6.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Speed Index 6.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Timing budget  
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more about performance budgets
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
First Contentful Paint 4.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Time to Interactive 8.1 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Total Blocking Time 460 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric

Does hector.network use compression? ▼

Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on hector.network are reduced by 83%.
hector.network use br compression.
Original size: 356.82 KB
Compressed size: 60.4 KB
File reduced by: 296.42 KB (83%)

Google Safe Browsing ▼

Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.
This site is not currently listed as suspicious

MyWot.com Reputation Ratings

MyWOT (short for "My Web of Trust") is a web-based reputation and rating service that provides users with information about the trustworthiness and safety of websites.
Status:
  UNKNOWN

SSL Checker - SSL Certificate Verify ▼

An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's web browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. hector.network supports HTTPS.
 hector.network supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: hector.network
Organization:
Location:
Issuer: GTS CA 1P5
Valid from: Feb 21 14:52:51 2024 GMT
Valid until: May 21 14:52:50 2024 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: GTS CA 1P5
Organization: Google Trust Services LLC
Location: US
Issuer: GTS Root R1
Valid from: Aug 13 00:00:42 2020 GMT
Valid until: Sep 30 00:00:42 2027 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: GTS Root R1
Organization: Google Trust Services LLC
Location: US
Issuer: GlobalSign Root CA
Valid from: Jun 19 00:00:42 2020 GMT
Valid until: Jan 28 00:00:42 2028 GMT
Authority: CA:TRUE
Keysize: 4096 Bits

Verify HTTP/2 Support ▼

HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency.
 hector.network supports HTTP/2
     
Verifying HTTP/2.0 Support. Please wait...

Http Header ▼

HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server. 
date: Tue, 16 Apr 2024 07:31:01 GMT
content-type: text/html; charset=UTF-8
vary: Accept-Encoding,User-Agent,Host
x-powered-by: PHP/7.4.33
last-modified: Tue, 16 Apr 2024 01:39:01 GMT
cache-control: max-age=0
expires: Tue, 16 Apr 2024 07:31:01 GMT
access-control-allow-origin: *
access-control-allow-credentials: true
access-control-allow-methods: GET, POST, OPTIONS
access-control-allow-headers: DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type
cf-cache-status: DYNAMIC
report-to: {"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=sPZBFa0T17Y6RJLvTNdNQnGEl0Ct4A3hxYtdB%2BPbERFtCs1zKktjYrwpP2qYVGiGcTYWa6PAQqCMyrBA1%2BBdS%2F3Mkrjck4%2BYNAZD%2FcELDeGEX%2B7vT0Z8ecM21gpXX0HS"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
strict-transport-security: max-age=31536000; includeSubDomains
x-content-type-options: nosniff
server: cloudflare
cf-ray: 8752792eac19111a-ORD
content-encoding: br

DNS Lookup ▼

DNS entries (Domain Name System) are a critical component of the Internet infrastructure. They act as directories that translate human-readable domain names (such as example.com) to machine-readable IP addresses. DNS records are stored on DNS servers and help forward internet traffic efficiently.
Type Ip Target/Txt TTL
HINFO 3600
AAAA 2606:4700:20::681a:b97 230
AAAA 2606:4700:20::681a:a97 230
AAAA 2606:4700:20::ac43:49b5 230
A 104.26.11.151 230
A 172.67.73.181 230
A 104.26.10.151 230
NS lou.ns.cloudflare.com 3530
NS rose.ns.cloudflare.com 3530

Whois Lookup ▼

Domain WHOIS is a public database that provides information about domain names, including registered owners, contact information, domain registrars, registration and expiration dates, name servers, and other relevant information. Domain registration for this website began on July 9, 2022 and will expire on July 9, 2024 if not renewed. This website is now assigned through the registrar NAMECHEAP INC. The WHOIS data for this website's domain was last updated on July 11, 2023.
Domain Created:
2022-07-09
Domain Expires:
2024-07-09
Domain Updated:
2023-07-11
Domain Age:
2 years 5 months 3 days
Domain Registrar:
NAMECHEAP INC
Domain Owner:
Privacy service provided by Withheld for Privacy e
WhoIs:
 

Domain name: hector.network
Registry Domain ID: 48eb6a49878c40728f754a8e59c9d1db-DONUTS
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2023-07-11T09:51:04.98Z
Creation Date: 2022-07-09T14:04:04.80Z
Registrar Registration Expiration Date: 2024-07-09T14:04:04.80Z
Registrar: NAMECHEAP INC
Registrar IANA ID: 1068
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.9854014545
Reseller: NAMECHEAP INC
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: transferPeriod https://icann.org/epp#transferPeriod
Registry Registrant ID: 
Registrant Name: Redacted for Privacy
Registrant Organization: Privacy service provided by Withheld for Privacy ehf
Registrant Street: Kalkofnsvegur 2 
Registrant City: Reykjavik
Registrant State/Province: Capital Region
Registrant Postal Code: 101
Registrant Country: IS
Registrant Phone: +354.4212434
Registrant Phone Ext: 
Registrant Fax: 
Registrant Fax Ext: 
Registrant Email: email
Registry Admin ID: 
Admin Name: Redacted for Privacy
Admin Organization: Privacy service provided by Withheld for Privacy ehf
Admin Street: Kalkofnsvegur 2 
Admin City: Reykjavik
Admin State/Province: Capital Region
Admin Postal Code: 101
Admin Country: IS
Admin Phone: +354.4212434
Admin Phone Ext: 
Admin Fax: 
Admin Fax Ext: 
Admin Email: email
Registry Tech ID: 
Tech Name: Redacted for Privacy
Tech Organization: Privacy service provided by Withheld for Privacy ehf
Tech Street: Kalkofnsvegur 2 
Tech City: Reykjavik
Tech State/Province: Capital Region
Tech Postal Code: 101
Tech Country: IS
Tech Phone: +354.4212434
Tech Phone Ext: 
Tech Fax: 
Tech Fax Ext: 
Tech Email: email
Name Server: lou.ns.cloudflare.com
Name Server: rose.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-04-15T15:32:11.35Z