NYTIMES.COM The New York Times - Breaking News, World News & Multimedia


nytimes.com website information.

nytimes.com website servers are located in United States and are responding from following IP address 151.101.193.164. Check the full list of most visited websites located in United States.

nytimes.com domain name is registered by .COM top-level domain registry. See the other sites registred in .COM domain zone.

Following name servers are specified for nytimes.com domain:

  • ns1.p24.dynect.net
  • ns2.p24.dynect.net
  • dns-plx.ewr1.nytimes.com
  • ns4.p24.dynect.net
  • dns-plx.sea1.nytimes.com
  • ns3.p24.dynect.net

and probably website nytimes.com is hosted by dynect.net web hosting company. Check the complete list of other most popular websites hosted by dynect.net hosting company.

According to Alexa traffic rank the highest website nytimes.com position was 69 (in the world). The lowest Alexa rank position was 137. Now website nytimes.com ranked in Alexa database as number 113 (in the world).

Website nytimes.com Desktop speed measurement score (65/100) is better than the results of 42.38% of other sites shows that the page desktop performance can be improved.

nytimes.com Mobile usability score (93/100) is better than the results of 49.72% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of nytimes.com (63/100) is better than the results of 62.04% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Apr-21-2018 113-2
Apr-20-2018 111-4
Apr-19-2018 107-2
Apr-18-2018 10517
Apr-17-2018 122-14
Apr-16-2018 108-1
Apr-15-2018 1071

Advertisement

nytimes.com Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.


nytimes.com whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


Domain Name: NYTIMES.COM
Registry Domain ID: 91991_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2018-02-06T18:26:26Z
Creation Date: 1994-01-18T05:00:00Z
Registry Expiry Date: 2023-01-19T05:00:00Z
Registrar: MarkMonitor Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: abusecomplaints@markmonitor.com
Registrar Abuse Contact Phone: +1.2083895740
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: serverDeleteProhibited https://icann.org/epp#serverDeleteProhibited
Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
Domain Status: serverUpdateProhibited https://icann.org/epp#serverUpdateProhibited
Name Server: NS1.P24.DYNECT.NET
Name Server: NS2.P24.DYNECT.NET
Name Server: NS3.P24.DYNECT.NET
Name Server: NS4.P24.DYNECT.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2018-03-24T18:57:24Z

nytimes.com server information

Servers Location

nytimes.com desktop page speed rank

Last tested: 2016-06-12


Desktop Speed Medium
65/100

nytimes.com Desktop Speed Test Quick Summary


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

Your page has 5 blocking script resources and 5 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://cdn.optimizely.com/js/3338050995.js
https://a1.nyt.com/assets/homepage/20160606-033247…ation/lib/framework.js
https://int.nyt.com/applications/geoip/geo.min.js
http://int.nyt.com/applications/voicebox/assets/vo…7f0a614774031499e61.js
http://int.nyt.com/data/weekend_reads/weekendreads-20151221-v1.js

Optimize CSS Delivery of the following:

https://a1.nyt.com/assets/homepage/20160606-033247/css/homepage/styles.css
https://typeface.nyt.com/css/zam5nzz.css
http://int.nyt.com/applications/voicebox/assets/vo…2bbd27383ec1e35431.css
https://a1.nyt.com/fonts/css/fonts.css
https://a1.nyt.com/fonts/css/fonts.css

priority - 11 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://int.nyt.com/data/weekend_reads/weekendreads-20151221-v1.js (expiration not specified)
http://www.nytimes.com/svc/location/v1/current.json (expiration not specified)
https://a248.e.akamai.net/chartbeat.download.akama…102508/js/chartbeat.js (expiration not specified)
https://s1.nyt.com/ugc/comments/commentData.json (expiration not specified)
http://int.nyt.com/data/promotron/items/568c343162266c000100001e.js (1 second)
https://cdn.optimizely.com/js/3338050995.js (2 minutes)
https://static01.nyt.com/services/json/taxonomy/v2…k=jsonTaxonomyCallback (4.4 minutes)
https://graphics8.nytimes.com/packages/js/newsgrap…vb_dem_debate_one_data (4.5 minutes)
https://cdnssl.clicktale.net/www06/ptc/d5c0897e-13…8-8480-3c7020133c09.js (5 minutes)
https://www.nytimes.com/svc/weather/v2/current-and-seven-day-forecast.json (10 minutes)
http://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://www.nytimes.com/svc/message/v1/list/global.json?_=1465680573625 (15 minutes)
http://connect.facebook.net/en_US/fbevents.js (20 minutes)
http://platform.twitter.com/widgets.js (30 minutes)
http://js-agent.newrelic.com/nr-918.min.js (60 minutes)
http://medianet-d.openx.net/w/1.0/jstag?oxns=mNHB (60 minutes)
http://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
http://js.moatads.com/nyt952824751/moatad.js (3 hours)
http://cdn3.optimizely.com/js/geo2.js (8 hours)
https://z.moatads.com/nytdfp348531439194/moatad.js (10 hours)
https://z.moatads.com/googleessencenyt485873431/mo…ndefined&referral_bsg= (11.3 hours)
http://graphics8.nytimes.com/bi/js/analytics/show_ads.js (47.6 hours)

priority - 8 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 81.8KiB (72% reduction).

Compressing https://tagx.nytimes.com/?url=http%3A%2F%2Fwww.nyt…_buster_=1465680573958 could save 57KiB (75% reduction).
Compressing http://int.nyt.com/data/weekend_reads/weekendreads-20151221-v1.js could save 22.5KiB (66% reduction).
Compressing https://www.nytimes.com/svc/weather/v2/current-and-seven-day-forecast.json could save 2.3KiB (78% reduction).

priority - 8 Optimize images

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

Optimize the following images to reduce their size by 81.5KiB (70% reduction).

Losslessly compressing https://static01.nyt.com/images/2016/06/12/opinion…ay-mediumSquare149.jpg could save 32.3KiB (74% reduction).
Losslessly compressing https://static01.nyt.com/adx/images/ADS/41/40/ad.414027/welcome-ad-bg.png could save 27.6KiB (72% reduction).
Losslessly compressing https://static01.nyt.com/images/crosswords/crosswords_30x30.png could save 17.2KiB (99% reduction).
Losslessly compressing https://static01.nyt.com/images/2016/01/14/upshot/…9268-thumbStandard.png could save 1.8KiB (16% reduction).
Losslessly compressing https://a1.nyt.com/assets/homepage/20160606-033247…os/nyt-logo-185x26.png could save 1,007B (43% reduction).
Compressing and resizing https://static01.nyt.com/adx/images/ADS/41/40/ad.414027/cross_black.png could save 930B (86% reduction).
Losslessly compressing https://static01.nyt.com/newsgraphics/2015/02/25/e…election-2016-logo.png could save 690B (47% reduction).

priority - 3 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 32.6KiB (27% reduction).

Minifying https://tagx.nytimes.com/?url=http%3A%2F%2Fwww.nyt…_buster_=1465680573958 could save 20.2KiB (27% reduction).
Minifying http://int.nyt.com/data/weekend_reads/weekendreads-20151221-v1.js could save 8.2KiB (25% reduction).
Minifying https://static.nytimes.com/bi/js/analytics/EventTracker.js could save 2.1KiB (30% reduction) after compression.
Minifying https://static01.nyt.com/marketing/ADX/bar1/bar1_meter_count_v2.js could save 903B (43% reduction) after compression.
Minifying https://a1.nyt.com/assets/homepage/20160606-033247…ews/ad-view-manager.js could save 660B (44% reduction) after compression.
Minifying http://dc8xl0ndzn2cb.cloudfront.net/js/nytimes/v1/keywee.js could save 547B (13% reduction) after compression.

priority - 2 Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 40% of the final above-the-fold content could be rendered with the full HTML response.

priority - 0 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 3.3KiB (11% reduction).

Minifying http://www.nytimes.com/ could save 3.3KiB (11% reduction) after compression.

nytimes.com Desktop Resources

Total Resources196
Number of Hosts53
Static Resources139
JavaScript Resources66
CSS Resources4

nytimes.com Desktop Resource Breakdown

nytimes.com mobile page speed rank

Last tested: 2016-06-12


Mobile Speed Bad
63/100

nytimes.com Mobile Speed Test Quick Summary


priority - 35 Avoid landing page redirects

Your page has 3 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://nytimes.com/
http://www.nytimes.com/
http://mobile.nytimes.com/redirect?to-mobile=http%…es.com%2F%3Freferer%3D
http://mobile.nytimes.com/?referer=

priority - 12 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://mobile.nytimes.com/ads-success (expiration not specified)
https://a248.e.akamai.net/chartbeat.download.akama…102508/js/chartbeat.js (expiration not specified)
https://secure-assets.rubiconproject.com/static/psa/43.png (expiration not specified)
https://www.nytimes.com/svc/video/api/v3/video/100000004460439 (expiration not specified)
https://www.nytimes.com/svc/video/api/v3/video/100000004465923 (expiration not specified)
https://www.nytimes.com/svc/video/api/v3/video/100000004466105 (expiration not specified)
http://www.googletagservices.com/tag/js/gpt.js (15 minutes)
http://cdn.krxd.net/controltag?confid=IquZvfNl (20 minutes)
http://connect.facebook.net/en_US/fbevents.js (20 minutes)
http://beacon.krxd.net/cookie2json?callback=Krux.n…fault.kxjsonp_3pevents (30 minutes)
http://gum.criteo.com/sync?c=2&r=2&j=rp_onUserIdLoaded_374042_43 (60 minutes)
http://pagead2.googlesyndication.com/pagead/expans…ed.js?source=safeframe (60 minutes)
http://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
http://ads.rubiconproject.com/ad/12330.js (2.3 hours)
https://z.moatads.com/nytdfp348531439194/moatad.js (10 hours)

priority - 12 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 113.2KiB (72% reduction).

Compressing https://79423.analytics.edgekey.net/html5/akamaihtml5-min.js could save 71.9KiB (71% reduction).
Compressing https://tagx.nytimes.com/?url=http%3A%2F%2Fmobile.…_buster_=1465680565959 could save 39.1KiB (73% reduction).
Compressing http://www.nytimes.com/svc/recommendations/v3/pers…&loc=mobileweb&limit=3 could save 2.2KiB (68% reduction).

priority - 2 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 17.9KiB (28% reduction).

Minifying https://tagx.nytimes.com/?url=http%3A%2F%2Fmobile.…_buster_=1465680565959 could save 15.3KiB (29% reduction).
Minifying https://static.nytimes.com/bi/js/analytics/EventTracker.js could save 2.1KiB (30% reduction) after compression.
Minifying http://dc8xl0ndzn2cb.cloudfront.net/js/nytimes/v1/keywee.js could save 547B (13% reduction) after compression.

priority - 0 Optimize images

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

Optimize the following images to reduce their size by 607B (12% reduction).

Losslessly compressing https://secure-assets.rubiconproject.com/static/psa/43.png could save 607B (12% reduction).

nytimes.com Mobile Resources

Total Resources103
Number of Hosts47
Static Resources47
JavaScript Resources49
CSS Resources2

nytimes.com Mobile Resource Breakdown

nytimes.com mobile page usability

Last tested: 2016-06-12


Mobile Usability Good
93/100

nytimes.com Mobile Usability Test Quick Summary


priority - 6 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 id="header-login" class="header-login">SubscribeorMy accountLog in</div> is close to 1 other tap targets.

The tap target <div id="header-login" class="header-login">SubscribeorMy accountLog in</div> and 1 others are close to other tap targets.

The tap target <div id="header-login" class="header-login">SubscribeorMy accountLog in</div> and 1 others are close to other tap targets.

The tap target <div class="share-containe…ainer-homepage">SHAREShare on…ditShareCancel</div> and 22 others are close to other tap targets.

The tap target <a href="https://myacco…s-homepage-0-0" class="halt share-link">Log in to SaveRead Later</a> and 22 others are close to other tap targets.

The tap target <a href="javascript:;" class="share-link halt">Share</a> and 22 others are close to other tap targets.

The tap target <a href="/" class="active">Home</a> and 16 others are close to other tap targets.
The tap target <a href="http://www.nyt…F%3Freferer%3D">Subscribe</a> and 2 others are close to other tap targets.
The tap target <a href="http://www.nyt…ml?nytmobile=0">© 2016</a> is close to 1 other tap targets.

nytimes.com Mobile Resources

Total Resources103
Number of Hosts47
Static Resources47
JavaScript Resources49
CSS Resources2

nytimes.com Mobile Resource Breakdown

nytimes.com similar domains

Similar domains:
www.nytimes.com
www.nytimes.net
www.nytimes.org
www.nytimes.info
www.nytimes.biz
www.nytimes.us
www.nytimes.mobi
www.ytimes.com
www.nytimes.com
www.bytimes.com
www.nbytimes.com
www.bnytimes.com
www.hytimes.com
www.nhytimes.com
www.hnytimes.com
www.jytimes.com
www.njytimes.com
www.jnytimes.com
www.mytimes.com
www.nmytimes.com
www.mnytimes.com
www.ntimes.com
www.nttimes.com
www.nyttimes.com
www.ntytimes.com
www.ngtimes.com
www.nygtimes.com
www.ngytimes.com
www.nhtimes.com
www.nyhtimes.com
www.nutimes.com
www.nyutimes.com
www.nuytimes.com
www.nyimes.com
www.nyrimes.com
www.nytrimes.com
www.nyrtimes.com
www.nyfimes.com
www.nytfimes.com
www.nyftimes.com
www.nygimes.com
www.nytgimes.com
www.nyyimes.com
www.nytyimes.com
www.nyytimes.com
www.nytmes.com
www.nytumes.com
www.nytiumes.com
www.nytuimes.com
www.nytjmes.com
www.nytijmes.com
www.nytjimes.com
www.nytkmes.com
www.nytikmes.com
www.nytkimes.com
www.nytomes.com
www.nytiomes.com
www.nytoimes.com
www.nyties.com
www.nytines.com
www.nytimnes.com
www.nytinmes.com
www.nytijes.com
www.nytimjes.com
www.nytikes.com
www.nytimkes.com
www.nytims.com
www.nytimws.com
www.nytimews.com
www.nytimwes.com
www.nytimss.com
www.nytimess.com
www.nytimses.com
www.nytimds.com
www.nytimeds.com
www.nytimdes.com
www.nytimrs.com
www.nytimers.com
www.nytimres.com
www.nytime.com
www.nytimew.com
www.nytimesw.com
www.nytimee.com
www.nytimese.com
www.nytimees.com
www.nytimed.com
www.nytimesd.com
www.nytimez.com
www.nytimesz.com
www.nytimezs.com
www.nytimex.com
www.nytimesx.com
www.nytimexs.com
www.nytimea.com
www.nytimesa.com
www.nytimeas.com
www.nytimes.con

nytimes.com Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


nytimes.com TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.