FORTUNE.COM Fortune - Fortune 500 Daily & Breaking Business News

fortune.com Website Information

Daily Unique Visits: 18,606

Daily Page Views: 111,636

Income Per Day: $223

Estimated Value: $160,560

This website is located in United States and is using following IP address 13.33.151.126. See the complete list of popular websites hosted in United States.

fortune.com is registered under .COM top-level domain. Please check other sites in .COM zone.

Website fortune.com is using the following name servers:

  • ns4.p07.dynect.net
  • ns3.p07.dynect.net
  • ns1.p07.dynect.net
  • ns2.p07.dynect.net
  • ns-1235.awsdns-26.org
  • ns-179.awsdns-22.com
  • ns-1978.awsdns-55.co.uk
  • ns-641.awsdns-16.net

and is probably hosted by AMAZON-02 - Amazon.com, Inc., US. See the full list of other websites hosted by AMAZON-02 - Amazon.com, Inc., US.

The highest website fortune.com position in Alexa rank database was 1036 and the lowest rank position was 104305. Current position of fortune.com in Alexa rank database is 77084.

Desktop speed score of fortune.com (18/100) is better than the results of 1.93% of other sites and shows that the page desktop performance can be improved.

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

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

Advertisement

fortune.com Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


fortune.com whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


Domain Name: FORTUNE.COM
Registry Domain ID: 105970_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2017-12-13T13:58:15Z
Creation Date: 1994-06-02T04:00:00Z
Registry Expiry Date: 2019-06-01T04: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: NS-1235.AWSDNS-26.ORG
Name Server: NS-179.AWSDNS-22.COM
Name Server: NS-1978.AWSDNS-55.CO.UK
Name Server: NS-641.AWSDNS-16.NET
Name Server: NS1.P07.DYNECT.NET
Name Server: NS2.P07.DYNECT.NET
Name Server: NS3.P07.DYNECT.NET
Name Server: NS4.P07.DYNECT.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2018-03-23T18:33:44Z

fortune.com server information

Servers Location

fortune.com desktop page speed rank

Last tested: 2016-06-12


Desktop Speed Bad
18/100

fortune.com Desktop Speed Test Quick Summary


priority - 210 Optimize images

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

Optimize the following images to reduce their size by 2MiB (90% reduction).

Compressing and resizing https://fortunedotcom.files.wordpress.com/2016/06/…jpg?w=840&h=485&crop=1 could save 441KiB (99% reduction).
Compressing and resizing https://fortunedotcom.files.wordpress.com/2016/04/…jpg?w=840&h=485&crop=1 could save 256.6KiB (99% reduction).
Compressing and resizing https://fortunedotcom.files.wordpress.com/2016/06/…jpg?w=800&h=488&crop=1 could save 249KiB (97% reduction).
Compressing and resizing https://fortunedotcom.files.wordpress.com/2016/06/…gif?w=800&h=661&crop=1 could save 217.2KiB (84% reduction).
Compressing and resizing https://fortunedotcom.files.wordpress.com/2016/06/…jpg?w=840&h=485&crop=1 could save 177KiB (99% reduction).
Compressing and resizing https://fortunedotcom.files.wordpress.com/2016/01/…jpg?w=840&h=485&crop=1 could save 138.8KiB (99% reduction).
Compressing and resizing https://fortunedotcom.files.wordpress.com/2016/06/…png?w=800&h=299&crop=1 could save 133KiB (77% reduction).
Compressing and resizing https://fortunedotcom.files.wordpress.com/2016/06/539419506.jpg could save 123.7KiB (94% reduction).
Compressing and resizing https://fortunedotcom.files.wordpress.com/2016/05/…png?w=800&h=299&crop=1 could save 79.9KiB (83% reduction).
Compressing and resizing https://fortunedotcom.files.wordpress.com/2016/03/…jpg?w=800&h=299&crop=1 could save 62.3KiB (95% reduction).
Compressing and resizing https://fortunedotcom.files.wordpress.com/2016/06/…jpg?w=840&h=485&crop=1 could save 49.3KiB (92% reduction).
Compressing and resizing https://fortunedotcom.files.wordpress.com/2016/06/…jpg?w=840&h=485&crop=1 could save 27.7KiB (88% reduction).
Compressing and resizing https://fortunedotcom.files.wordpress.com/2016/06/…jpg?w=800&h=488&crop=1 could save 24.8KiB (88% reduction).
Losslessly compressing https://fortunedotcom.files.wordpress.com/2016/06/….jpg?w=90&h=120&crop=1 could save 17.6KiB (51% reduction).
Compressing and resizing https://fortunedotcom.files.wordpress.com/2016/03/tully.png?w=150 could save 14.3KiB (76% reduction).
Compressing and resizing https://fortunedotcom.files.wordpress.com/2014/05/kell.png?w=150 could save 13.7KiB (76% reduction).
Compressing and resizing https://fortunedotcom.files.wordpress.com/2016/03/hackett-robert.png?w=150 could save 13.6KiB (76% reduction).
Losslessly compressing https://fortunedotcom.files.wordpress.com/2015/08/…jpg?w=820&h=570&crop=1 could save 10.3KiB (19% reduction).
Losslessly compressing http://markets.fortune.com/images/minichart4.png could save 2.7KiB (60% reduction).

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

Compressing http://fortune.com/ could save 773.3KiB (72% reduction).
Compressing http://fortune.com/data/headlines/ could save 44.1KiB (76% reduction).
Compressing http://fortune.com/data/menu/dropdown/ could save 23.4KiB (86% reduction).

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

Your page has 18 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://cdn.optimizely.com/js/3391221358.js
https://r-login.wordpress.com/remote-login.php?act…3A%2F%2Ffortune.com%2F
https://s2.wp.com/_static/??-eJyFztEKwjAMBdAfsqsVH…90cNverfdu0+/iCzQBW8w=
http://tiads.fortune.com/ads/tgx.js?ver=1.1
http://tiads.timeinc.net/ads/tii_bk-coretag.js
http://tiads.timeinc.net/ads/subsbk.js
http://partner.googleadservices.com/gpt/pubads_impl_89.js
http://pq-direct.revsci.net/pql?placementIdList=Dr…zFgKb&cb=1465717062855
http://platform.linkedin.com/in.js
https://s1.wp.com/wp-content/mu-plugins/likes/queuehandler.js?m=1438290161h
http://platform.twitter.com/widgets.js?ver=20111117
https://s0.wp.com/_static/??-eJyVyzEOgCAMAMAPiRXjA…5yznYanPfOjja/csovZQ==
http://tags.tiqcdn.com/utag/timeinc/fortune.com/prod/utag.js?ver=4.5.2
https://s1.wp.com/_static/??/wp-includes/js/jquery…t.min.js?m=1433512424j
http://www.googleadservices.com/pagead/conversion.js?ver=4.5.2
https://s1.wp.com/_static/??-eJyFzMEKwjAQBNAfMl1it…pebv40Xi9nP05TegOya149
https://s0.wp.com/_static/??-eJyVzUEOgzAMRNELARYtF…Fqu9ezb8ehe/g/m6Bj0w==

Use asynchronous versions of the following scripts:

http://www.googletagservices.com/tag/js/gpt.js

Optimize CSS Delivery of the following:

https://s0.wp.com/_static/??-eJx9jUEOgkAMAD9kLSIxe…8QtnYFC+?cssminify=yes
http://fonts.timeinc.net/ti/fortune/webfonts.css?ver=1.0.00
https://s0.wp.com/_static/??-eJyVj9EKwjAMRX/IGqab4…A3YEcfY=?cssminify=yes
http://img5.timeinc.net/hat/css/style.min.css

priority - 21 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://ak.sail-horizon.com/horizon/v1.js (expiration not specified)
http://c.betrad.com/geo/c.js (expiration not specified)
https://secure-assets.rubiconproject.com/static/ps…/RUBICON-300x250-2.jpg (expiration not specified)
http://fortune.com/data/menu/dropdown/ (56 seconds)
http://cdn.optimizely.com/js/3391221358.js (2 minutes)
http://fortune.com/data/headlines/ (2.5 minutes)
http://tags.tiqcdn.com/utag/timeinc/fortune.com/prod/utag.js?ver=4.5.2 (5 minutes)
http://www.googletagservices.com/tag/js/gpt.js (15 minutes)
http://connect.facebook.net/en_US/all.js (20 minutes)
http://connect.facebook.net/en_US/fbds.js (20 minutes)
http://platform.twitter.com/widgets.js?ver=20111117 (30 minutes)
http://tags.tiqcdn.com/utag/tiqapp/utag.v.js?a=tim…01807&cb=1465717063091 (30 minutes)
http://ads.rubiconproject.com/ad/7810.js (42.6 minutes)
http://admin.brightcove.com/js/BrightcoveExperiences.js?ver=1.0.1 (60 minutes)
http://d3qxwzhswv93jk.cloudfront.net/esf.js (60 minutes)
http://gum.criteo.com/sync?c=2&r=2&j=rp_onUserIdLoaded_156644_15 (60 minutes)
http://js-agent.newrelic.com/nr-632.min.js (60 minutes)
http://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
http://tiads.fortune.com/ads/tgx.js (60 minutes)
http://tiads.fortune.com/ads/tgx.js?ver=1.1 (60 minutes)
http://tiads.timeinc.net/ads/evidon.js (60 minutes)
http://tiads.timeinc.net/ads/subsbk.js (60 minutes)
http://tiads.timeinc.net/ads/tii_bk-coretag.js (60 minutes)
https://a248.e.akamai.net/f/1016/606/2d/tiads-ssl.…nc.net/ads/img/1x1.png (60 minutes)
http://static.chartbeat.com/js/chartbeat.js (2 hours)
https://z.moatads.com/timeincdfp92367299557/moatad.js (7.7 hours)
http://s.moatads.com/timeinccontent193iZxR31/moatcontent.js?firstimp_bsg=1 (11.8 hours)
http://markets.fortune.com/css/boilerplate.css (24 hours)
http://markets.fortune.com/css/idc-common.css (24 hours)
http://markets.fortune.com/css/idc-fluid.css (24 hours)
http://markets.fortune.com/css/idc-fonts.css (24 hours)
http://markets.fortune.com/css/jquery-ui.css (24 hours)
http://markets.fortune.com/css/reset-orchard.css (24 hours)
http://markets.fortune.com/css/type/helveticaneueltstd-mdcn-webfont.woff (24 hours)
http://markets.fortune.com/images/minichart4.png (24 hours)
http://markets.fortune.com/js/advancedchart.js (24 hours)
http://markets.fortune.com/js/idc-jquery-ui-functions.js (24 hours)
http://markets.fortune.com/js/jquery.idms-quoteTiles.js (24 hours)
http://markets.fortune.com/js/ko-custom-bindings.js (24 hours)
http://markets.fortune.com/js/lib/moment/moment.js (24 hours)
http://markets.fortune.com/js/lib/numeralJs/numeral-1.5.1.min.js (24 hours)
http://markets.fortune.com/js/modernizr-2.6.2-respond-1.1.0.min.js (24 hours)
http://markets.fortune.com/js/respond.min.js (24 hours)
http://markets.fortune.com/js/responsiveTooltip/jquery.responsiveTooltip.js (24 hours)
http://markets.fortune.com/js/staticchart.js (24 hours)

priority - 16 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 157.6KiB (39% reduction).

Minifying http://www.charting.idmanagedsolutions.com/static/…s/lib/highstock.src.js could save 66KiB (50% reduction) after compression.
Minifying http://code.jquery.com/jquery-1.9.1.js could save 37.8KiB (49% reduction) after compression.
Minifying http://code.jquery.com/ui/1.10.3/jquery-ui.js could save 37.2KiB (36% reduction) after compression.
Minifying https://s2.wp.com/_static/??-eJyFztEKwjAMBdAfsqsVH…90cNverfdu0+/iCzQBW8w= could save 6.2KiB (13% reduction) after compression.
Minifying http://tiads.fortune.com/ads/tgx.js could save 3.5KiB (25% reduction) after compression.
Minifying http://tiads.fortune.com/ads/tgx.js?ver=1.1 could save 3.5KiB (25% reduction) after compression.
Minifying http://tiads.timeinc.net/ads/tii_bk-coretag.js could save 1.3KiB (14% reduction) after compression.
Minifying http://markets.fortune.com/js/advancedchart.js could save 782B (18% reduction) after compression.
Minifying http://markets.fortune.com/js/staticchart.js could save 702B (22% reduction) after compression.
Minifying http://markets.fortune.com/js/ko-custom-bindings.js could save 534B (31% reduction) after compression.

priority - 12 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 53% of the final above-the-fold content could be rendered with the full HTML response.

priority - 0 Minify CSS

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

Minify CSS for the following resources to reduce their size by 3.4KiB (25% reduction).

Minifying http://markets.fortune.com/css/boilerplate.css could save 1.3KiB (49% reduction) after compression.
Minifying http://markets.fortune.com/css/jquery-ui.css could save 1.2KiB (19% reduction) after compression.
Minifying http://markets.fortune.com/css/idc-common.css could save 987B (20% reduction) after compression.

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 614B (20% reduction).

Minifying http://markets.fortune.com/application/index/indices could save 614B (20% reduction) after compression.

fortune.com Desktop Resource Breakdown

Total Resources208
Number of Hosts74
Static Resources121
JavaScript Resources105
CSS Resources10

fortune.com mobile page speed rank

Last tested: 2016-06-12


Mobile Speed Bad
29/100

fortune.com Mobile Speed Test Quick Summary


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

Your page has 9 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://cdn.optimizely.com/js/3391221358.js
https://r-login.wordpress.com/remote-login.php?act…3A%2F%2Ffortune.com%2F
https://s2.wp.com/_static/??-eJyFztEKwjAMBdAfsqsVH…90cNverfdu0+/iCzQBW8w=
http://tiads.fortune.com/ads/tgx.js?ver=1.1
http://tiads.timeinc.net/ads/tii_bk-coretag.js
http://tiads.timeinc.net/ads/subsbk.js
http://partner.googleadservices.com/gpt/pubads_impl_89.js
http://pq-direct.revsci.net/pql?placementIdList=Dr…zFgKb&cb=1465717052376

Use asynchronous versions of the following scripts:

http://www.googletagservices.com/tag/js/gpt.js

Optimize CSS Delivery of the following:

https://s0.wp.com/_static/??-eJx9jUEOgkAMAD9kLSIxe…8QtnYFC+?cssminify=yes
http://fonts.timeinc.net/ti/fortune/webfonts.css?ver=1.0.00
https://s0.wp.com/_static/??-eJyVj9EKwjAMRX/IGqab4…A3YEcfY=?cssminify=yes

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

Compressing http://fortune.com/ could save 773.3KiB (72% reduction).
Compressing http://fortune.com/data/headlines/ could save 44.1KiB (76% reduction).
Compressing http://fortune.com/data/menu/dropdown/ could save 23.4KiB (86% reduction).

priority - 29 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://ak.sail-horizon.com/horizon/v1.js (expiration not specified)
http://c.betrad.com/geo/c.js (expiration not specified)
http://fortune.com/data/menu/dropdown/ (expiration not specified)
http://cdn.optimizely.com/js/3391221358.js (2 minutes)
http://fortune.com/data/headlines/ (5 minutes)
http://tags.tiqcdn.com/utag/timeinc/fortune.com/prod/utag.js?ver=4.5.2 (5 minutes)
http://www.googletagservices.com/tag/js/gpt.js (15 minutes)
http://connect.facebook.net/en_US/all.js (20 minutes)
http://connect.facebook.net/en_US/fbds.js (20 minutes)
http://platform.twitter.com/widgets.js?ver=20111117 (30 minutes)
http://tags.tiqcdn.com/utag/tiqapp/utag.v.js?a=tim…01807&cb=1465717052563 (30 minutes)
http://admin.brightcove.com/js/BrightcoveExperiences.js?ver=1.0.1 (60 minutes)
http://d3qxwzhswv93jk.cloudfront.net/esf.js (60 minutes)
http://js-agent.newrelic.com/nr-632.min.js (60 minutes)
http://pagead2.googlesyndication.com/pagead/expans…ed.js?source=safeframe (60 minutes)
http://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
http://tiads.fortune.com/ads/tgx.js (60 minutes)
http://tiads.fortune.com/ads/tgx.js?ver=1.1 (60 minutes)
http://tiads.timeinc.net/ads/evidon.js (60 minutes)
http://tiads.timeinc.net/ads/subsbk.js (60 minutes)
http://tiads.timeinc.net/ads/tii_bk-coretag.js (60 minutes)
https://a248.e.akamai.net/f/1016/606/2d/tiads-ssl.…nc.net/ads/img/1x1.png (60 minutes)
http://static.chartbeat.com/js/chartbeat.js (2 hours)
http://s.moatads.com/timeinccontent193iZxR31/moatcontent.js?firstimp_bsg=1 (11.8 hours)
http://markets.fortune.com/css/boilerplate.css (24 hours)
http://markets.fortune.com/css/idc-common.css (24 hours)
http://markets.fortune.com/css/idc-fluid.css (24 hours)
http://markets.fortune.com/css/idc-fonts.css (24 hours)
http://markets.fortune.com/css/jquery-ui.css (24 hours)
http://markets.fortune.com/css/reset-orchard.css (24 hours)
http://markets.fortune.com/css/type/helveticaneueltstd-mdcn-webfont.woff (24 hours)
http://markets.fortune.com/images/minichart4.png (24 hours)
http://markets.fortune.com/js/advancedchart.js (24 hours)
http://markets.fortune.com/js/idc-jquery-ui-functions.js (24 hours)
http://markets.fortune.com/js/jquery.idms-quoteTiles.js (24 hours)
http://markets.fortune.com/js/ko-custom-bindings.js (24 hours)
http://markets.fortune.com/js/lib/moment/moment.js (24 hours)
http://markets.fortune.com/js/lib/numeralJs/numeral-1.5.1.min.js (24 hours)
http://markets.fortune.com/js/modernizr-2.6.2-respond-1.1.0.min.js (24 hours)
http://markets.fortune.com/js/respond.min.js (24 hours)
http://markets.fortune.com/js/responsiveTooltip/jquery.responsiveTooltip.js (24 hours)
http://markets.fortune.com/js/staticchart.js (24 hours)

priority - 16 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 157.6KiB (39% reduction).

Minifying http://www.charting.idmanagedsolutions.com/static/…s/lib/highstock.src.js could save 66KiB (50% reduction) after compression.
Minifying http://code.jquery.com/jquery-1.9.1.js could save 37.8KiB (49% reduction) after compression.
Minifying http://code.jquery.com/ui/1.10.3/jquery-ui.js could save 37.2KiB (36% reduction) after compression.
Minifying https://s2.wp.com/_static/??-eJyFztEKwjAMBdAfsqsVH…90cNverfdu0+/iCzQBW8w= could save 6.2KiB (13% reduction) after compression.
Minifying http://tiads.fortune.com/ads/tgx.js could save 3.5KiB (25% reduction) after compression.
Minifying http://tiads.fortune.com/ads/tgx.js?ver=1.1 could save 3.5KiB (25% reduction) after compression.
Minifying http://tiads.timeinc.net/ads/tii_bk-coretag.js could save 1.3KiB (14% reduction) after compression.
Minifying http://markets.fortune.com/js/advancedchart.js could save 782B (18% reduction) after compression.
Minifying http://markets.fortune.com/js/staticchart.js could save 702B (22% reduction) after compression.
Minifying http://markets.fortune.com/js/ko-custom-bindings.js could save 534B (31% reduction) after compression.

priority - 6 Optimize images

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

Optimize the following images to reduce their size by 54.2KiB (24% reduction).

Losslessly compressing https://fortunedotcom.files.wordpress.com/2016/06/539419506.jpg could save 23.5KiB (18% reduction).
Losslessly compressing https://fortunedotcom.files.wordpress.com/2016/06/….jpg?w=90&h=120&crop=1 could save 17.6KiB (51% reduction).
Losslessly compressing https://fortunedotcom.files.wordpress.com/2015/08/…jpg?w=820&h=570&crop=1 could save 10.3KiB (19% reduction).
Losslessly compressing http://markets.fortune.com/images/minichart4.png could save 2.7KiB (60% reduction).

priority - 0 Minify CSS

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

Minify CSS for the following resources to reduce their size by 3.4KiB (25% reduction).

Minifying http://markets.fortune.com/css/boilerplate.css could save 1.3KiB (49% reduction) after compression.
Minifying http://markets.fortune.com/css/jquery-ui.css could save 1.2KiB (19% reduction) after compression.
Minifying http://markets.fortune.com/css/idc-common.css could save 987B (20% reduction) after compression.

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 614B (20% reduction).

Minifying http://markets.fortune.com/application/index/indices could save 614B (20% reduction) after compression.

fortune.com Mobile Resource Breakdown

Total Resources176
Number of Hosts67
Static Resources109
JavaScript Resources85
CSS Resources11

fortune.com mobile page usability

Last tested: 2016-06-12


Mobile Usability Good
98/100

fortune.com Mobile Usability Test Quick Summary


priority - 2 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 <a class="rhimage"></a> is close to 1 other tap targets.

The tap target <span class="rhpromotext rhdefaultcolored">Nordea mobilā lietotne</span> is close to 1 other tap targets.

The tap target <div class="rhstoreicon"></div> is close to 2 other tap targets.

The tap target <div id="abgc" class="abgc">AdChoices</div> is close to 1 other tap targets.

The tap target <a href="/2016/06/11/ve…-schlumberger/">Venezuela PDVS…erger Presence</a> is close to 1 other tap targets.

The tap target <a href="http://fortune…obert-hackett/">Robert Hackett</a> and 2 others are close to other tap targets.
The tap target <tr class="clickableRow i…w idc-firstrow">DOW…(-0.67%)</tr> is close to 1 other tap targets.
The tap target <a href="http://fortune…iid=hp_mktdata">See All Market Activity</a> is close to 1 other tap targets.
The tap target <a href="http://fortune.com/venture/">Venture</a> and 3 others are close to other tap targets.
The tap target <a href="http://fortune.com/fortune500/">Fortune 500</a> and 9 others are close to other tap targets.
The tap target <a href="http://subscri…ehavioral.html">Ad Choices</a> and 10 others are close to other tap targets.
The tap target <a href="http://www.morningstar.com/">Morningstar, Inc.</a> is close to 1 other tap targets.
The tap target <img id="_evh-ric-c" src="http://c.betra…/ric-close.png"> is close to 1 other tap targets.

The tap target <p id="_evh-learn">Learn More</p> is close to 1 other tap targets.

fortune.com Mobile Resource Breakdown

Total Resources176
Number of Hosts67
Static Resources109
JavaScript Resources85
CSS Resources11

fortune.com HTML validation

Errors

Stray start tag “html”.

Line: 14 Column: 45 - 16
"...) ]><!--> <html lang="en"> <!--<..."

A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.

Line: 18 Column: 1 - 73
"...s</title> <meta http-equiv="X-UA-Compatible" content="IE=9; IE=8; IE=7; IE=EDGE" /> <meta..."

Bad value “asyc” for attribute “async” on element “script”.

Line: 187 Column: 1 - 126
"...</script> <script async='asyc' type='text/javascript' src='http://admin.brightcove.com/js/BrightcoveExperiences.js?ver=1.0.1#asyncload'></scri..." Line: 912 Column: 1 - 105
"...</script> <script async='asyc' type='text/javascript' src='//widgets.outbrain.com/outbrain.js?ver=4.9.1#asyncload'></scri..."

The text content of element “time” was not in the required format: The literal did not satisfy the time-datetime format.

Line: 325 Column: 32 - 38
"...:58 AM EST</time> ..." Line: 330 Column: 32 - 38
"...:31 AM EST</time> ..." Line: 335 Column: 32 - 38
"...:39 AM EST</time> ..." Line: 346 Column: 52 - 58
"...:39 AM EST</time> ..." Line: 363 Column: 32 - 38
"...:58 AM EST</time> ..." Line: 368 Column: 32 - 38
"...:31 AM EST</time> ..." Line: 373 Column: 32 - 38
"...:39 AM EST</time> ..." Line: 473 Column: 49 - 55
"...:01 PM EST</time> ..." Line: 485 Column: 30 - 36
"...:12 AM EST</time> ..." Line: 497 Column: 30 - 36
"...:48 AM EST</time> ..."

The “scrolling” attribute on the “iframe” element is obsolete. Use CSS instead.

Line: 509 Column: 10 - 104
"... <iframe scrolling="no" frameborder="0" class="fortune-fullwidth" style="background-color:gray"></ifra..." Line: 514 Column: 12 - 160
"... <iframe width="900" scrolling="no" height="422" frameborder="0" marginwidth="0" marginheight="0" style="border: 0px none; vertical-align: bottom;" ></ifra..."

The “frameborder” attribute on the “iframe” element is obsolete. Use CSS instead.

Line: 509 Column: 10 - 104
"... <iframe scrolling="no" frameborder="0" class="fortune-fullwidth" style="background-color:gray"></ifra..." Line: 514 Column: 12 - 160
"... <iframe width="900" scrolling="no" height="422" frameborder="0" marginwidth="0" marginheight="0" style="border: 0px none; vertical-align: bottom;" ></ifra..." Line: 683 Column: 4 - 187
".../form> <iframe id="fortune_newsletter_submit_message" name="fortune_newsletter_submit_message" src="javascript:false;" width="620" height="200" frameBorder="0" style="display:none;" seamless></ifra..."

The “marginwidth” attribute on the “iframe” element is obsolete. Use CSS instead.

Line: 514 Column: 12 - 160
"... <iframe width="900" scrolling="no" height="422" frameborder="0" marginwidth="0" marginheight="0" style="border: 0px none; vertical-align: bottom;" ></ifra..."

The “marginheight” attribute on the “iframe” element is obsolete. Use CSS instead.

Line: 514 Column: 12 - 160
"... <iframe width="900" scrolling="no" height="422" frameborder="0" marginwidth="0" marginheight="0" style="border: 0px none; vertical-align: bottom;" ></ifra..."

Bad value “generator nofollow” for attribute “rel” on element “a”: The string “generator” is not a registered keyword.

Line: 582 Column: 19 - 220
"...owered by <a href="https://vip.wordpress.com/?utm_source=vip_powered_wpcom&#038;utm_medium=web&#038;utm_campaign=VIP%20Footer%20Credit&#038;utm_term=fortune.com" rel="generator nofollow" class="powered-by-wpcom">WordPr..." Line: 612 Column: 18 - 219
"...owered by <a href="https://vip.wordpress.com/?utm_source=vip_powered_wpcom&#038;utm_medium=web&#038;utm_campaign=VIP%20Footer%20Credit&#038;utm_term=fortune.com" rel="generator nofollow" class="powered-by-wpcom">WordPr..."

Attribute “seamless” not allowed on element “iframe” at this point.

Line: 683 Column: 4 - 187
".../form> <iframe id="fortune_newsletter_submit_message" name="fortune_newsletter_submit_message" src="javascript:false;" width="620" height="200" frameBorder="0" style="display:none;" seamless></ifra..."

The “itemprop” attribute was specified, but the element is not a property of any item.

Line: 342 Column: 89 - 199
"...ce-guys/"><img src="https://fortunedotcom.files.wordpress.com/2017/11/gettyimages-880553146.jpg" itemprop="image" alt=""></a> ..."

Warnings

Consider avoiding viewport values that prevent users from resizing documents.

Line: 20 Column: 1 - 87
"...UTF-8" /> <meta name="viewport" content="width=device-width,minimum-scale=1.0,maximum-scale=1.0"> <meta..."

The “banner” role is unnecessary for element “header”.

Line: 223 Column: 2 - 43
"...ht"> <header class="main-header" role="banner"> <di..."

Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.

Line: 319 Column: 11 - 57
"... <section class="featured-articles home-module"> ..." Line: 409 Column: 11 - 54
"... <section class="package-bottom home-module"> ..." Line: 318 Column: 10 - 44
"... <section class="package package-a"> ..."

The “contentinfo” role is unnecessary for element “footer”.

Line: 554 Column: 1 - 41
"...ary --> <footer id="colophon" role="contentinfo"> <di..."

This document appears to be written in English. Consider adding “lang="en"” (or variant) to the “html” start tag.

Line: 12 Column: 23 - 43
"...E 9]><!--> <html class="no-js"> <!--<..."

fortune.com similar domains

Similar domains:
www.fortune.com
www.fortune.net
www.fortune.org
www.fortune.info
www.fortune.biz
www.fortune.us
www.fortune.mobi
www.ortune.com
www.fortune.com
www.cortune.com
www.fcortune.com
www.cfortune.com
www.dortune.com
www.fdortune.com
www.dfortune.com
www.rortune.com
www.frortune.com
www.rfortune.com
www.tortune.com
www.ftortune.com
www.tfortune.com
www.gortune.com
www.fgortune.com
www.gfortune.com
www.vortune.com
www.fvortune.com
www.vfortune.com
www.frtune.com
www.firtune.com
www.foirtune.com
www.fiortune.com
www.fkrtune.com
www.fokrtune.com
www.fkortune.com
www.flrtune.com
www.folrtune.com
www.flortune.com
www.fprtune.com
www.foprtune.com
www.fportune.com
www.fotune.com
www.foetune.com
www.foretune.com
www.foertune.com
www.fodtune.com
www.fordtune.com
www.fodrtune.com
www.foftune.com
www.forftune.com
www.fofrtune.com
www.fottune.com
www.forttune.com
www.fotrtune.com
www.forune.com
www.forrune.com
www.fortrune.com
www.forrtune.com
www.forfune.com
www.fortfune.com
www.forgune.com
www.fortgune.com
www.forgtune.com
www.foryune.com
www.fortyune.com
www.forytune.com
www.fortne.com
www.fortyne.com
www.fortuyne.com
www.forthne.com
www.fortuhne.com
www.forthune.com
www.fortjne.com
www.fortujne.com
www.fortjune.com
www.fortine.com
www.fortuine.com
www.fortiune.com
www.fortue.com
www.fortube.com
www.fortunbe.com
www.fortubne.com
www.fortuhe.com
www.fortunhe.com
www.fortuje.com
www.fortunje.com
www.fortume.com
www.fortunme.com
www.fortumne.com
www.fortun.com
www.fortunw.com
www.fortunew.com
www.fortunwe.com
www.fortuns.com
www.fortunes.com
www.fortunse.com
www.fortund.com
www.fortuned.com
www.fortunde.com
www.fortunr.com
www.fortuner.com
www.fortunre.com
www.fortune.con

fortune.com Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


fortune.com TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.