nytimes.com Nytimes.com - Archive.nytimes.com

   
The New York Times Web Archive

Domain Summary

What is the traffic rank for Archive.nytimes.com?

• Archive.nytimes.com ranks #18 globally on HypeStat.

What IP addresses does Archive.nytimes.com resolve to?

• Archive.nytimes.com resolves to the IP addresses 146.75.93.164.

Where are Archive.nytimes.com servers located in?

• Archive.nytimes.com has servers located in Los Angeles, California, 90012, United States.

archive.nytimes.com Profile

Title:The New York Times Web Archive

What technologies does archive.nytimes.com use?

These are the technologies used at archive.nytimes.com. archive.nytimes.com has a total of 3 technologies installed in 3 different categories.

archive.nytimes.com Traffic Analysis

Archive.nytimes.com is ranked #18 in the world.
Daily Visitors n/a
Monthly Visits n/a
Pages per Visit n/a
Visit duration n/a
Bounce Rate n/a
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
 n/a
Monthly Visits:
n/a
Pages per Visit:
n/a
Daily Pageviews:
n/a
Avg. visit duration:
n/a
Bounce rate:
n/a
Global Reach:
 n/a
HypeRank:
18
SEMrush Rank:
18
*All traffic values are estimates only.
Last update was 307 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with nytimes.com 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:
  archive.nytimes.com
Rank:
(Rank based on keywords, cost and organic traffic)
  18
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  26,322,074
Organic Traffic:
(Number of visitors coming from top 20 search results)
  185,103,291
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $210,817,452.00

Ad Experience Report

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

Mobile summary

Root domain:
nytimes.com
Last Change Time:
(The last time that the site changed status.)
2022-03-04 04:48:25
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.)
Passing

Desktop summary

Root domain:
nytimes.com
Last Change Time:
(The last time that the site changed status.)
2020-02-12 05:07:52
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.)
Passing

Abusive Experience Report

Summary of the abusive experience rating of a website.
Root domain:
nytimes.com
Last Change Time:
(The last time that the site changed status.)
2020-02-12 05:07:52
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.)
Passing

Where is archive.nytimes.com hosted?

Archive.nytimes.com may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
146.75.93.164
ASN:
AS54113 
ISP:
Fastly 
Server Location:
Los Angeles
California, CA
90012
United States, US
 

Other sites hosted on 146.75.93.164

How fast does archive.nytimes.com load?

The average loading time of archive.nytimes.com is 246 ms. The Desktop speed index is 100 and mobile speed index is 99.
Average Load Time:
246 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 FAST 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)1.1s 89% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 89% 5% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 5% 5% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 5%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%

Origin Data

All pages served from this origin have an FAST 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% 4% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 4%
First Input Delay (FID)4ms 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%

Lab Data

Does not have 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
Avoids `unload` event listeners  
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more
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
Largest Contentful Paint 0.6 s
Largest Contentful Paint marks the time at which the largest 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
Speed Index 0.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
Time to Interactive 0.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
First Meaningful Paint 0.6 s
First Meaningful Paint measures when the primary content of a page is visible. 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. 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
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more
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 more

Page Speed (Google PageSpeed Insights) - Mobile

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

First Contentful Paint (FCP)2.1s 89% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 67% 20% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 20% 11% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 11%
First Input Delay (FID)224ms 54% of loads for this page have a fast (<100ms) First Input Delay (FID) 54% 38% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 38% 6% of loads for this page have a slow (>300ms) First Input Delay (FID) 6%

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)2.1s 67% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 67% 20% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 20% 11% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 11%
First Input Delay (FID)224ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 54% 38% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 38% 6% of loads for this page have a slow (>300ms) First Input Delay (FID) 6%

Lab Data

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
Does not have 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
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
Speed Index 1.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
Largest Contentful Paint 1.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Avoids `unload` event listeners  
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more
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 more
First Contentful Paint (3G) 3060 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more
First Meaningful Paint 2.2 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
First Contentful Paint 1.6 s
First Contentful Paint marks the time at which the first text or image is painted. 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. Learn more
Time to Interactive 2.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more

Does archive.nytimes.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 archive.nytimes.com are reduced by 56%.
archive.nytimes.com use gzip compression.
Original size: 2.86 KB
Compressed size: 1.24 KB
File reduced by: 1.62 KB (56%)

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. archive.nytimes.com has 93 Safety Reputations.
Status:
  SAFE
Safety Reputations:
  93
Safety Confidence:
  14
Child Safety Reputations:
  93
Child Safety Confidence:
  33

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. archive.nytimes.com supports HTTPS.
 archive.nytimes.com supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: nytimes.com
Organization:
Location:
Issuer: Thawte RSA CA 2018
Valid from: Mar 22 00:00:00 2023 GMT
Valid until: Apr 21 23:59:59 2024 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: Thawte RSA CA 2018
Organization: DigiCert Inc, OU = www.digicert.com
Location: US
Issuer: DigiCert Global Root CA
Valid from: Nov 6 12:23:52 2017 GMT
Valid until: Nov 6 12:23:52 2027 GMT
Authority: CA:TRUE
Keysize: 2048 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.
 archive.nytimes.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.
x-guploader-uploadid: ADPycdt5DSXei76hA6N8ZGjZno2XVaVAX-ER-6GhomFvqsmeglOHKKoZ0N9svSNJ4X3ZrP8NKAl8zxKCEVynx1iXp0e31bis83dQ
x-goog-generation: 1522358344295179
x-goog-metageneration: 1
x-goog-stored-content-encoding: identity
x-goog-stored-content-length: 2932
x-goog-hash: crc32c=ymuhEg==
x-goog-hash: md5=C/EkIPwszDBC2P+K9tCSWQ==
x-goog-storage-class: MULTI_REGIONAL
server: UploadServer
expires: Wed, 14 Jun 2023 09:20:28 GMT
cache-control: public, max-age=3600
last-modified: Thu, 29 Mar 2018 21:19:04 GMT
etag: "0bf12420fc2ccc3042d8ff8af6d09259"
content-type: text/html
content-encoding: gzip
accept-ranges: bytes
date: Fri, 30 Jun 2023 10:09:09 GMT
via: 1.1 varnish
age: 1093
x-served-by: cache-bur-kbur8200104-BUR
x-cache: HIT
x-cache-hits: 1
x-timer: S1688119750.947014,VS0,VE1
vary: Accept-Encoding
x-api-version: 
content-security-policy: upgrade-insecure-requests; default-src data: 'unsafe-inline' 'unsafe-eval' https:; script-src data: 'unsafe-inline' 'unsafe-eval' https: blob:; style-src data: 'unsafe-inline' https:; img-src data: https: blob: android-webview-video-poster:; font-src data: https:; connect-src https: wss: blob:; media-src data: https: blob:; object-src https:; child-src https: data: blob:; form-action https:; report-uri https://csp.nytimes.com/report;
strict-transport-security: max-age=63072000; preload; includeSubdomains
content-length: 1271

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
CNAME nytimes.map.fastly.net 90

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.
WhoIs:
 

No match for "ARCHIVE.NYTIMES.COM".
>>> Last update of whois database: 2023-01-18T23:33:16Z