WILLAMETTE.COM Willamette Management Associates, A Citizens company - Business Valuation Firm

willamette.com Website Information

Daily Unique Visits: 763

Daily Page Views: 1,526

Income Per Day: $5

Estimated Value: $1,200

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

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

Website willamette.com is using the following name servers:

  • ns2.comcastbusiness.net
  • ns3.comcastbusiness.net
  • ns4.comcastbusiness.net
  • ns5.comcastbusiness.net
  • ns1.comcastbusiness.net

and is probably hosted by DATAPIPE-SEA - DataPipe, Inc., US. See the full list of other websites hosted by DATAPIPE-SEA - DataPipe, Inc., US.

The highest website willamette.com position in Alexa rank database was 73870 and the lowest rank position was 999579. Current position of willamette.com in Alexa rank database is 940424.

Desktop speed score of willamette.com (84/100) is better than the results of 78.07% of other sites and shows that the page is performing great on desktop computers.

Mobile usability score of willamette.com (67/100) is better than the results of 18.73% of other sites and means that the page is not mobile-friendly.

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

Advertisement

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


willamette.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: WILLAMETTE.COM
Registry Domain ID: 4949366_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2022-03-25T21:13:09Z
Creation Date: 1995-03-28T05:00:00Z
Registry Expiry Date: 2028-03-29T04:00:00Z
Registrar: MarkMonitor Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: abusecomplaints@markmonitor.com
Registrar Abuse Contact Phone: +1.2086851750
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Name Server: A1-203.AKAM.NET
Name Server: A13-64.AKAM.NET
Name Server: A18-65.AKAM.NET
Name Server: A20-66.AKAM.NET
Name Server: A22-67.AKAM.NET
Name Server: A9-64.AKAM.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2022-08-24T19:08:27Z

willamette.com server information

Servers Location

willamette.com desktop page speed rank

Last tested: 2019-12-01


Desktop Speed Medium
84/100

willamette.com Desktop Speed Test Quick Summary


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

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

Remove render-blocking JavaScript:

http://ajax.googleapis.com/ajax/libs/jquery/1.6.0/jquery.min.js
http://willamette.com/js/modernizr.js

Optimize CSS Delivery of the following:

http://willamette.com/css/wma.css
http://willamette.com/css/willamette.css
http://willamette.com/css/dropdown.css
http://fonts.googleapis.com/css?family=Niconne

priority - 6Optimize images

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

Optimize the following images to reduce their size by 58.4KiB (57% reduction).

Losslessly compressing http://willamette.com/tools/twitter.jpg could save 15KiB (92% reduction).
Losslessly compressing http://willamette.com/media/images/yearly-award.jpg could save 13.7KiB (80% reduction).
Losslessly compressing http://willamette.com/insights/images/winter_2016_big.jpg could save 13.2KiB (49% reduction).
Losslessly compressing http://willamette.com/images/book_intangible_index.jpg could save 9.9KiB (32% reduction).
Losslessly compressing http://willamette.com/images/willamette_management_associates_logo.png could save 2.6KiB (55% reduction).
Losslessly compressing http://www.google.com/cse/static/en/google_custom_search_watermark.gif could save 1.4KiB (69% reduction).
Losslessly compressing https://www.google.com/uds/css/small-logo.png could save 1.1KiB (72% reduction).
Losslessly compressing https://www.google.com/uds/css/v2/clear.png could save 874B (85% reduction).
Losslessly compressing https://www.google.com/uds/css/v2/search_box_icon.png could save 842B (82% reduction).

priority - 2Leverage 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://cse.google.com/adsense/search/async-ads.js (60 minutes)
http://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
https://www.google.com/jsapi?autoload=%7B%22module…22%3A%22en%22%7D%5D%7D (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)

priority - 1Minify 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 4.4KiB (35% reduction).

Minifying https://www.google.com/uds/api/search/1.0/432dd570…54f9ca1/default+en.css could save 3.9KiB (40% reduction) after compression.
Minifying https://cse.google.com/cse/style/look/v2/default.css could save 530B (18% reduction) after compression.

priority - 0Minify 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 2.8KiB (2% reduction).

Minifying https://www.gstatic.com/swiffy/v6.0/runtime.js could save 1.5KiB (2% reduction) after compression.
Minifying https://www.google.com/uds/api/search/1.0/432dd570…4f9ca1/default+en.I.js could save 823B (1% reduction) after compression.
Minifying http://cse.google.com/adsense/search/async-ads.js could save 589B (1% reduction) after compression.

willamette.com Desktop Resource Breakdown

Total Resources35
Number of Hosts9
Static Resources11
JavaScript Resources9
CSS Resources6

willamette.com mobile page speed rank

Last tested: 2019-11-20


Mobile Speed Medium
70/100

willamette.com Mobile Speed Test Quick Summary


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

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

Remove render-blocking JavaScript:

http://ajax.googleapis.com/ajax/libs/jquery/1.6.0/jquery.min.js
http://willamette.com/js/modernizr.js

Optimize CSS Delivery of the following:

http://willamette.com/css/wma.css
http://willamette.com/css/willamette.css
http://willamette.com/css/dropdown.css
http://fonts.googleapis.com/css?family=Niconne

priority - 6Optimize images

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

Optimize the following images to reduce their size by 58.4KiB (57% reduction).

Losslessly compressing http://willamette.com/tools/twitter.jpg could save 15KiB (92% reduction).
Losslessly compressing http://willamette.com/media/images/yearly-award.jpg could save 13.7KiB (80% reduction).
Losslessly compressing http://willamette.com/insights/images/winter_2016_big.jpg could save 13.2KiB (49% reduction).
Losslessly compressing http://willamette.com/images/book_intangible_index.jpg could save 9.9KiB (32% reduction).
Losslessly compressing http://willamette.com/images/willamette_management_associates_logo.png could save 2.6KiB (55% reduction).
Losslessly compressing http://www.google.com/cse/static/en/google_custom_search_watermark.gif could save 1.4KiB (69% reduction).
Losslessly compressing https://www.google.com/uds/css/small-logo.png could save 1.1KiB (72% reduction).
Losslessly compressing https://www.google.com/uds/css/v2/clear.png could save 874B (85% reduction).
Losslessly compressing https://www.google.com/uds/css/v2/search_box_icon.png could save 842B (82% reduction).

priority - 3Leverage 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://cse.google.com/adsense/search/async-ads.js (60 minutes)
http://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
https://www.google.com/jsapi?autoload=%7B%22module…22%3A%22en%22%7D%5D%7D (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)

priority - 1Minify 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 4.4KiB (35% reduction).

Minifying https://www.google.com/uds/api/search/1.0/432dd570…54f9ca1/default+en.css could save 3.9KiB (40% reduction) after compression.
Minifying https://cse.google.com/cse/style/look/v2/default.css could save 530B (18% reduction) after compression.

priority - 0Minify 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 2.8KiB (2% reduction).

Minifying https://www.gstatic.com/swiffy/v6.0/runtime.js could save 1.5KiB (2% reduction) after compression.
Minifying https://www.google.com/uds/api/search/1.0/432dd570…4f9ca1/default+en.I.js could save 823B (1% reduction) after compression.
Minifying http://cse.google.com/adsense/search/async-ads.js could save 589B (1% reduction) after compression.

willamette.com Mobile Resource Breakdown

Total Resources35
Number of Hosts9
Static Resources11
JavaScript Resources9
CSS Resources6

willamette.com mobile page usability

Last tested: 2019-11-20


Mobile Usability Medium
67/100

willamette.com Mobile Usability Test Quick Summary


priority - 40Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

CONTACT renders only 6 pixels tall (16 CSS pixels).

About Our Firm and 4 others render only 6 pixels tall (16 CSS pixels).

A national bus…and Portland. renders only 6 pixels tall (16 CSS pixels).

Upcoming Events and 1 others render only 7 pixels tall (19 CSS pixels).

August and 2 others render only 6 pixels tall (16 CSS pixels).

11-12 and 2 others render only 7 pixels tall (19 CSS pixels).

Forensic & Val…ion Conference and 7 others render only 6 pixels tall (16 CSS pixels).

American Bar A…ls in Taxation and 2 others render only 4 pixels tall (13 CSS pixels).

Focus on Gift…Tax Valuation and 1 others render only 6 pixels tall (16 CSS pixels).

READ MORE renders only 6 pixels tall (16 CSS pixels).

Insights renders only 7 pixels tall (19 CSS pixels).

Latest Issue: renders only 6 pixels tall (16 CSS pixels).

Winter 2016 renders only 6 pixels tall (16 CSS pixels).

Insights wins…year in a row renders only 4 pixels tall (11 CSS pixels).

March 2014- A…January 2014. and 18 others render only 6 pixels tall (16 CSS pixels).

Guide to Intan…sset Valuation and 4 others render only 6 pixels tall (16 CSS pixels).

© renders only 4 pixels tall (11 CSS pixels).
2015 Willamett…ent Associates renders only 4 pixels tall (11 CSS pixels).
About Our Firm and 6 others render only 4 pixels tall (11 CSS pixels).

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

priority - 0Size 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 href="https://twitter.com/willamette"></a> is close to 1 other tap targets.
The tap target <a href="http://www.lin…24936?trk=tyah"></a> is close to 1 other tap targets.

willamette.com HTML validation

Warnings

The “navigation” role is unnecessary for element “nav”.

Line: 253 Column: 1 - 52
"...ation --> <nav class="navbar navbar-inverse navbar-fixed-top" role="navigation" style="background-color:#007C66;"> <div ..."

A table row was 0 columns wide, which is less than the column count established by the first row (1).

Line: 458 Column: 15 - 8
"...></tr><tr> </table> <hr>..." Line: 479 Column: 15 - 8
"...></tr><tr> </table> <hr> ..." Line: 501 Column: 15 - 8
"...></tr><tr> </table> <hr> ..." Line: 520 Column: 15 - 8
"...></tr><tr> </table><hr> <..."

Errors

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Line: 265 Column: 22 - 47
"...dex.html"><img src="images/wma.png"></a> <..." Line: 397 Column: 32 - 57
"...n:center"><img class="img-responsive" src="images/wma-responsive.png" height="120" width="360"> <br>..."

Row 4 of a row group established by a “tbody” element has no cells beginning on it.

Line: 458 Column: 15 - 8
"...></tr><tr> </table> <hr>..." Line: 479 Column: 15 - 8
"...></tr><tr> </table> <hr> ..." Line: 501 Column: 15 - 8
"...></tr><tr> </table> <hr> ..." Line: 520 Column: 15 - 8
"...></tr><tr> </table><hr> <..."

Stray end tag “a”.

Line: 513 Column: 1 - 4
"...nference </a><br> <..."

End tag “p” implied, but there were open elements.

Line: 603 Column: 1 - 3
"...n a row <p><a hre..."

Unclosed element “a”.

Line: 596 Column: 4 - 71
"... </p> <p><a href="http://www.willamette.com/media/releases2/apex_2017_release.pdf"><span ..." Line: 604 Column: 4 - 76
"... row <p><a href="http://www.willamette.com/media/releases2/abi_book_2d_ed_release.pdf"><span ..."

Start tag “a” seen but an element of the same type was already open.

Line: 604 Column: 4 - 76
"... row <p><a href="http://www.willamette.com/media/releases2/abi_book_2d_ed_release.pdf"><span ..." Line: 609 Column: 4 - 69
"...</p> <p><a href="http://www.willamette.com/media/releases2/ramirez_release.pdf"><span ..."

No “a” element in scope but a “a” end tag seen.

Line: 604 Column: 4 - 76
"... row <p><a href="http://www.willamette.com/media/releases2/abi_book_2d_ed_release.pdf"><span ..."

End tag “p” seen, but there were open elements.

Line: 605 Column: 179 - 182
"...tion</em> </p> <p>..."

End tag “a” violates nesting rules.

Line: 609 Column: 4 - 69
"...</p> <p><a href="http://www.willamette.com/media/releases2/ramirez_release.pdf"><span ..."

Cannot recover after last error. Any further errors will be ignored.

Line: 609 Column: 4 - 69
"...</p> <p><a href="http://www.willamette.com/media/releases2/ramirez_release.pdf"><span ..."

willamette.com similar domains

Similar domains:
www.willamette.com
www.willamette.net
www.willamette.org
www.willamette.info
www.willamette.biz
www.willamette.us
www.willamette.mobi
www.illamette.com
www.willamette.com
www.qillamette.com
www.wqillamette.com
www.qwillamette.com
www.aillamette.com
www.waillamette.com
www.awillamette.com
www.sillamette.com
www.wsillamette.com
www.swillamette.com
www.eillamette.com
www.weillamette.com
www.ewillamette.com
www.wllamette.com
www.wullamette.com
www.wiullamette.com
www.wuillamette.com
www.wjllamette.com
www.wijllamette.com
www.wjillamette.com
www.wkllamette.com
www.wikllamette.com
www.wkillamette.com
www.wollamette.com
www.wiollamette.com
www.woillamette.com
www.wilamette.com
www.wiplamette.com
www.wilplamette.com
www.wipllamette.com
www.wiolamette.com
www.wilolamette.com
www.wiklamette.com
www.wilklamette.com
www.wilpamette.com
www.willpamette.com
www.wiloamette.com
www.willoamette.com
www.wilkamette.com
www.willkamette.com
www.willmette.com
www.willqmette.com
www.willaqmette.com
www.willqamette.com
www.willwmette.com
www.willawmette.com
www.willwamette.com
www.willsmette.com
www.willasmette.com
www.willsamette.com
www.willzmette.com
www.willazmette.com
www.willzamette.com
www.willaette.com
www.willanette.com
www.willamnette.com
www.willanmette.com
www.willajette.com
www.willamjette.com
www.willajmette.com
www.willakette.com
www.willamkette.com
www.willakmette.com
www.willamtte.com
www.willamwtte.com
www.willamewtte.com
www.willamwette.com
www.willamstte.com
www.willamestte.com
www.willamsette.com
www.willamdtte.com
www.willamedtte.com
www.willamdette.com
www.willamrtte.com
www.willamertte.com
www.willamrette.com
www.willamete.com
www.willamerte.com
www.willametrte.com
www.willamefte.com
www.willametfte.com
www.willameftte.com
www.willamegte.com
www.willametgte.com
www.willamegtte.com
www.willameyte.com
www.willametyte.com
www.willameytte.com
www.willametre.com
www.willamettre.com
www.willametfe.com
www.willamettfe.com
www.willametge.com
www.willamettge.com
www.willametye.com
www.willamettye.com
www.willamett.com
www.willamettw.com
www.willamettew.com
www.willamettwe.com
www.willametts.com
www.willamettes.com
www.willamettse.com
www.willamettd.com
www.willametted.com
www.willamettde.com
www.willamettr.com
www.willametter.com
www.willamette.con

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


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