npmtrends.com Npmtrends.com

   
Npm trends: Compare NPM package downloads

Domain Summary

What is the traffic rank for Npmtrends.com?

• Npmtrends.com ranks #819,417 globally on HypeStat.

What percent of global Internet users visit Npmtrends.com?

• 0.0001604% of global Internet users visit Npmtrends.com

How many people visit Npmtrends.com each day?

• Npmtrends.com receives approximately 7.9K visitors and 21,275 page impressions per day.

Which countries does Npmtrends.com receive most of its visitors from?

• Npmtrends.com is mostly visited by people located in United States,Brazil,Germany.

How much Npmtrends.com can earn?

• Npmtrends.com should earn about $74.02/day from advertising revenue.

What is Npmtrends.com estimated value?

• Estimated value of Npmtrends.com is $73,947.40.

What IP addresses does Npmtrends.com resolve to?

• Npmtrends.com resolves to the IP addresses 76.76.21.21.

Where are Npmtrends.com servers located in?

• Npmtrends.com has servers located in Walnut, California, 91789, United States.

npmtrends.com Profile

Title:npm trends: Compare NPM package downloads
Description:Which NPM package should you use? Compare packages download stats, bundle sizes, github stars and more. Spot trends, pick the winner.
About: Npmtrends.com is a website that provides data and insights into the usage of npm packages. It allows users to compare the popularity of different packages, view the most popular packages, and track the trends of packages over time. It also provides information on the number of downloads, stars, and forks for each package. Additionally, users can search for packages by keyword and filter results by language, license, and other criteria.
*This text is generated by artificial intelligence and may not be accurate. Edit Site Info

What technologies does npmtrends.com use?

These are the technologies used at npmtrends.com. npmtrends.com has a total of 6 technologies installed in 6 different categories.
Font Scripts
Font Awesome Font Awesome
Web Frameworks
Next.js Next.js
Web Servers
Next.js Next.js
Vercel Vercel
JavaScript Frameworks
React React
Miscellaneous
webpack webpack
Programming Languages
Node.js Node.js

npmtrends.com Traffic Analysis

Npmtrends.com is ranked #819,417 in the world. This website is viewed by an estimated 7.9K visitors daily, generating a total of 21.3K pageviews. This equates to about 239.6K monthly visitors. Npmtrends.com traffic has increased by 31.08% compared to last month.
Daily Visitors7.9K
2.73%
Monthly Visits239.6K
31.08%
Pages per Visit2.69
5.43%
Visit duration01:00
46.79%
Bounce Rate56.91%
5.75%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
7,909
Monthly Visits:
239,643
Pages per Visit:
2.69
Daily Pageviews:
21,275
Avg. visit duration:
01:00
Bounce rate:
56.91%
Global Reach:
0.0001604%
Monthly Visits (SEMrush):
184,164
Monthly Unique Visitors (SEMrush):
119,200
Monthly Visits (SimilarWeb):
234,915
HypeRank:
819,417
SEMrush Rank:
219,921
SimilarWeb Rank:
205,861
*All traffic values are estimates only.

Traffic sources

Direct:
11.25%
Referral:
3.05%
Search:
84.02%
Social:
1.68%
Paid:
0%

Desktop vs Mobile

Desktop:
84.09%
Mobile:
15.91%

Total Visits Last 3 Months

248.6K
DEC
182.8K
JAN
239.6K
FEB

Visitors by country

Country
Users%
 
United States 8.44%
 
Brazil 5.71%
 
Germany 5.46%
 
India 5.36%
 
China 4.08%

Where do visitors go on npmtrends.com?

 
Reach%Pageviews%PerUser
npmtrends.com
100.00%100.00%2.8
Last update was 386 days ago
     
This can take up to 60 seconds. Please wait...

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

Search Engine Indexes ▼

Search engine indexes are huge databases or collections of net pages that search engines like google like google and yahoo use to retrieve applicable facts while customers carry out searches. These indexes are created through search engines like google and yahoo through crawling and indexing net pages from throughout the internet.
Google Index:
70,500
Bing Index:
16,300
Baidu Index:
2,110

  ▼

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:
  npmtrends.com
Rank:
(Rank based on keywords, cost and organic traffic)
  219,921
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  15,833
Organic Traffic:
(Number of visitors coming from top 20 search results)
  7,537
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $5,276.00
Full SEMrush Report >>

Revenue report ▼

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

How much would npmtrends.com make?

Daily Revenue:
$74.02
Monthly Revenue:
$2,220.60
Yearly Revenue:
$27,017.30
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 1,795$8.67
 
Germany 1,162$1.63
 
Brazil 1,215$1.62
 
India 1,140$0.43
 
China 868$0.09

Loss of money due to Adblock?

Daily Revenue Loss:
$2.26
Monthly Revenue Loss:
$67.86
Yearly Revenue Loss:
$825.62
Daily Pageviews Blocked:
1,165
Monthly Pageviews Blocked:
34,946
Yearly Pageviews Blocked:
425,172

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 323$1.56
 
Germany 337$0.47
 
India 319$0.12
 
Brazil 73$0.10
 
China 113$0.01

How much is npmtrends.com worth?

Website Value:
$73.9K

Ad Experience Report ▼

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

Mobile summary

Root domain:
npmtrends.com
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:
npmtrends.com
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:
npmtrends.com
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 npmtrends.com hosted? ▼

Npmtrends.com may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
76.76.21.21
ASN:
AS16509 
ISP:
Amazon.com, Inc. 
Server Location:
Walnut
California, CA
91789
United States, US
 

Other sites hosted on 76.76.21.21

How fast does npmtrends.com load? ▼

The average loading time of npmtrends.com is 73 ms. The Desktop speed index is 100 and mobile speed index is 80.
Average Load Time:
73 ms

Page Speed (Google PageSpeed Insights) - Desktop

100
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.

First Contentful Paint (FCP)677ms 95% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 95% 2% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 2% 2% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 2%
First Input Delay (FID)3ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 99% 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%

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.

First Contentful Paint (FCP)1.5s 84% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 84% 11% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 11% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
First Input Delay (FID)3ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 99% 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%

Lab Data

Max Potential First Input Delay 90 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay 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
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
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
First Meaningful Paint 0.5 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
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
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 about the Time to Interactive metric
Has a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
Speed Index 0.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 0.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint 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
First Contentful Paint 0.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Total Blocking Time 20 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

Page Speed (Google PageSpeed Insights) - Mobile

80
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.

First Contentful Paint (FCP)898ms 95% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 94% 1% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 1% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
First Input Delay (FID)18ms 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%

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.

First Contentful Paint (FCP)1.7s 79% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 79% 16% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 16% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
First Input Delay (FID)15ms 99% 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%

Lab Data

First Meaningful Paint 1.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
First Contentful Paint (3G) 3419.0225830078125 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more about the First Contentful Paint (3G) metric
Speed Index 1.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index 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
Total Blocking Time 630 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
Time to Interactive 4.7 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
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
Has a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
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
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
First Contentful Paint 1.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Max Potential First Input Delay 320 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay 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
Largest Contentful Paint 2.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric

Does npmtrends.com 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 npmtrends.com are reduced by 70%.
npmtrends.com use br compression.
Original size: 8.62 KB
Compressed size: 2.53 KB
File reduced by: 6.08 KB (70%)

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. npmtrends.com supports HTTPS.
 npmtrends.com supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: npmtrends.com
Organization:
Location:
Issuer: R3
Valid from: Mar 26 08:03:23 2023 GMT
Valid until: Jun 24 08:03:22 2023 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R3
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Sep 4 00:00:00 2020 GMT
Valid until: Sep 15 16:00:00 2025 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: ISRG Root X1
Organization: Internet Security Research Group
Location: US
Issuer: DST Root CA X3
Valid from: Jan 20 19:14:03 2021 GMT
Valid until: Sep 30 18:14:03 2024 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.
 npmtrends.com 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. 
age: 34865
cache-control: public, max-age=0, must-revalidate
content-encoding: br
content-security-policy: default-src 'self' pl-proxy.uidotdev.workers.dev npm-trends-proxy.uidotdev.workers.dev; connect-src 'self' bytes.dev npm-trends-proxy.uidotdev.workers.dev npm-trends-gateway.onrender.com connect.facebook.net pl-proxy.uidotdev.workers.dev; script-src 'self' use.fortawesome.com connect.facebook.net npm-trends-proxy.uidotdev.workers.dev pl-proxy.uidotdev.workers.dev 'unsafe-eval' 'unsafe-inline'; style-src 'self' use.fortawesome.com 'unsafe-inline'; img-src 'self' https: data:; font-src 'self' data:;
content-type: text/html; charset=utf-8
date: Thu, 30 Mar 2023 02:14:43 GMT
server: Vercel
strict-transport-security: max-age=63072000
x-matched-path: /[[...packets]]
x-powered-by: Next.js
x-vercel-cache: HIT
x-vercel-id: cle1::iad1::wf8s2-1680177348841-8b28fd487d5b
x-xss-protection: 1; mode=block

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
SOA 3468
Mname ns-cloud-e1.googledomains.com
Rname cloud-dns-hostmaster.google.com
Serial Number 21
Refresh 21600
Retry 3600
Expire 259200
Minimum TTL 300
A 76.76.21.21 3468
NS ns-cloud-e1.googledomains.com 3467
NS ns-cloud-e4.googledomains.com 3467
NS ns-cloud-e3.googledomains.com 3467
NS ns-cloud-e2.googledomains.com 3467

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 December 1, 2015 and will expire on December 1, 2023 if not renewed. This website is now assigned through the registrar Google LLC. The WHOIS data for this website's domain was last updated on July 2, 2022.
Domain Created:
2015-12-01
Domain Expires:
2023-12-01
Domain Updated:
2022-07-02
Domain Age:
8 years 4 months 18 days
Domain Registrar:
Google LLC
Domain Owner:
Contact Privacy Inc. Customer 7151571251
WhoIs:
 

Domain Name: npmtrends.com
Registry Domain ID: 1985134212_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.google.com
Registrar URL: https://domains.google.com
Updated Date: 2022-07-02T20:27:14Z
Creation Date: 2015-12-02T04:37:29Z
Registrar Registration Expiration Date: 2023-12-02T04:37:29Z
Registrar: Google LLC
Registrar IANA ID: 895
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.8772376466
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: Contact Privacy Inc. Customer 7151571251
Registrant Organization: Contact Privacy Inc. Customer 7151571251
Registrant Street: 96 Mowat Ave
Registrant City: Toronto
Registrant State/Province: ON
Registrant Postal Code: M4K 3K1
Registrant Country: CA
Registrant Phone: +1.4165385487
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: https://domains.google.com/contactregistrant?domain=npmtrends.com
Registry Admin ID:
Admin Name: Contact Privacy Inc. Customer 7151571251
Admin Organization: Contact Privacy Inc. Customer 7151571251
Admin Street: 96 Mowat Ave
Admin City: Toronto
Admin State/Province: ON
Admin Postal Code: M4K 3K1
Admin Country: CA
Admin Phone: +1.4165385487
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: https://domains.google.com/contactregistrant?domain=npmtrends.com
Registry Tech ID:
Tech Name: Contact Privacy Inc. Customer 7151571251
Tech Organization: Contact Privacy Inc. Customer 7151571251
Tech Street: 96 Mowat Ave
Tech City: Toronto
Tech State/Province: ON
Tech Postal Code: M4K 3K1
Tech Country: CA
Tech Phone: +1.4165385487
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: https://domains.google.com/contactregistrant?domain=npmtrends.com
Name Server: NS-CLOUD-E1.GOOGLEDOMAINS.COM
Name Server: NS-CLOUD-E2.GOOGLEDOMAINS.COM
Name Server: NS-CLOUD-E3.GOOGLEDOMAINS.COM
Name Server: NS-CLOUD-E4.GOOGLEDOMAINS.COM
DNSSEC: signedDelegation
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2023-03-30T11:55:33.142330Z