website SEO analysis & review tools logo

website SEO analysis & review tools

Options
allAll
successHigh score
mediumMedium score
lowLow score
infoInfo only
socialSocial
backlinksBacklinks
visitorsVisitors
accessibilityAccessibility
SEO-contentSEO-content
technologyTechnology
validityValidity
usabilityUsability
SEOSEO
mobileMobile
performancePerformance
SEO-AuthoritySEO-Authority
securitySecurity

Report for cbmmortgage.com

iwebchk

Top Priorities

list
Please SUBSCRIBE to see the full list of personalized tasks.
Show more Show less

Traffic Rank

visitors
4,097,608 most visited website in the World Trend: down (+4,568,580)
Traffic Rank is provided by Alexa

Visitors Localization

visitors
No data available.
Registering country code top level domains (ccTLD) can prevent potential competitors from taking advantage of your primary domain reputation. It is also one of the ways to improve country specific SEO and performance. (www.searchenginejournal.com/seo-without-boarders-a-guide-to-international-seo-nick-paterman/60092/)

Images

accessibilitySEO-content
Perfect, all images have ALT attribute.
Number of images: 9
Missing alt tag: 0
The "alt" attribute provides a text equivalent for the image. If the browser cannot display an image the alt description will be given in its place. Furthermore, some visitors cannot see images as they might be blind in which the alt tag provides a valuable image description. Finally, search engines utilize the alt attribute for image search indexing. (www.w3.org/QA/Tips/altAttribute)

Title

SEO-content
We have found following title:

"CBM Mortgage - Home Loans | Winchester VA, Strasburg VA, Front Royal VA"

Length: 71 characters
The <TITLE> element provides a short piece of text describing the document. The title is very important as it shows in the window title bars, bookmarks and search results. Title should be between 60 to 80 characters long. (www.w3.org/QA/Tips/good-titles)

Description Metatag

SEO-content
We have found following description:

"Your mortgage lender for Front Royal, Strasburg & Winchester, VA. Our specialists work side-by-side with you to get the best home loan for your needs."

Length: 150 characters
The description attribute should provide a concise explanation of a Web page's content. Also, the description is often displayed on search engine results and can indirectly affect page ranking.

Keywords Metatag

SEO-content
We have found 6 keywords:
  • first-time homebuyer
  • home loan
  • mortgage lender
  • front royal va
  • strasburg va
  • winchester va
    Length: 93 characters
    The keywords attribute was utilized by search engines to provide more accurate search results. Due to the over usage and spamming the keywords attribute has been phased out and is no longer relevant. Google doesn't use the "keywords" meta tag in web search ranking.

    Text to HTML Ratio

    SEO-content
    The Text to HTML ratio is 16.64%
    Original content is by far the single most important element to search engines. Low Text to HTML ratio indicates little content for search engines to index. We consider it to be good practice to have a Text to HTML ratio of at least 10% and ideal above 20%

    Keyword Density & Consistency

    SEO-content
    Consistent Keywords % Density # Count T Title D Desc. H <H> A ALT B <b>
    mortgage4.54%2611542
    loan2.62%15-11--
    home1.92%11111-1
    cbm1.92%111-131
    shalt1.75%10-----
    thou1.75%10-----
    get1.57%9-1--1
    front0.87%511--2
    strasburg0.87%511--2
    royal0.87%511--2
    cbm mortgage1.92%111-1--
    thou shalt1.75%10-----
    front royal0.87%511---
    home loan0.70%4-11--
    mortgage company0.52%3--1--
    mbs issuance rankings0.17%1--1--
    data validation products0.17%1--1--
    loan originator directory0.17%1-----
    tough personnel decisions0.17%1-----
    making tough personnel0.17%1-----
    Keywords density and consistency are notable factors for optimal page SEO. Preferred keywords should have higher keywords density indicating their importance. Optimally, preferred keywords should also be consistently utilized in multiple essential areas of the page such as title, description meta tag, h1 through h6 headings, alt image attributes, backlinks and internal links anchor text. Keyword density of above 6% can indicate that the word or a phrase appears too many time in the content.

    Frames

    accessibilitySEO-content
    No frames detected. We found 1 inline frame(s).
    It is not recommended to use frames or iframes because they can cause problems for search engines. It is best to avoid frames and inline frames whenever possible (searchenginewatch.com/article/2064573/Search-Engines-and-Frames). If frames must be utilized consider <noframes> tag. (www.w3schools.com/tags/tag_noframes.asp).

    Flash

    accessibilitytechnologySEO-content
    No flash detected.
    Flash and other reach-media technologies should primarily be utilized for decorative purposes. This makes your site more search engine friendly and improves accessibility (support.google.com/webmasters/bin/answer.py?hl=en&answer=72746#1).

    Headings

    SEO-content
    • 1 <H1>
      • Welcome to CBM Mortgage
    • 3 <H2>
      • What We Do
      • How Do You Choose the Right Mortgage Company?
      • Home Loan Programs
    • 5 <H3>
      • Follow Us
      • Upcoming Events; Mortgage and Bank Announcements; MBS Issuance Rankings
      • Construction and Data Validation Products; FHA, VA, HECM Changes
      • State-Level Policy Updates; Eyes on Fed Rate Increase
      • Licensed in Virginia, West Virginia, and Maryland.
    • 2 <H4>
      • Latest Mortgage News Headlines
      • Shopping around for the best mortgage rates? Ask these 10 questions before choosing a lender.
    • 0 <H5>
    • 0 <H6>
    The <h1> to <h6> tags are used to define HTML headings. The <h1> tag should hold the title describing the content of a specific page therefore only one h1 tag is needed per page. There can be any number of h2 - h6 tags but they should be added in order of importance (www.w3schools.com/tags/tag_hn.asp).

    Doctype

    technologyvalidity
    HTML 5
    The <!DOCTYPE> declaration tells the web browser about what version of HTML the page is written in. It is good practice to always add the <!DOCTYPE> declaration to the HTML documents, so that the browser knows what type of document to expect. (www.w3schools.com/tags/tag_DOCTYPE.asp)

    Character Encoding

    technologyvalidity
    UTF-8 (Unicode)
    Covers: Worldwide
    To display an HTML page correctly, the browser must know what character-set to use.

    Language

    usability
    Declared Language: en-gb (English)
    Language Attribute: en-gb (English)
    The HTML "lang" attributes and language metatag define the base language to be used for displaying text and characters on a Website.

    W3C Markup Validation

    validity
    Status: FAILED [8 errors, 3 warning(s)]
    It is good practice to use valid HTML/XHTML markup as it ensures that the search engines can read the website correctly as well as it improves cross browser compatibility (W3C Markup Validation Service).

    Deprecated HTML elements

    technologyvalidity
    Good, no deprecated elements found.
    A deprecated element is one that has been outdated by newer constructs. Deprecated elements may become obsolete in future versions of HTML so it is recommended not to use them.

    Nested HTML Tables

    accessibilitytechnology
    Great, no nested tables detected.
    In general it is not recommended to use nested tables or to utilize tables for page layout. Nested tables are known to cause performance issues due to increased HTML size and rendering time. It is better to use CSS layout instead.

    Web Analytics

    technology
    Yes, we have detected following web analytics tools:
    • Google analytics icon Google™ Analytics
    Web Analytics Tools collect and measure information about visitor activity on a website. Well interpreted web traffic data is invaluable in determining a successfully web strategy and assessing the effectiveness of a website. At a minimum, we recommend to utilize at least one web analytics tool.

    robots.txt

    SEO
    Yes, http://cbmmortgage.com/robots.txt

    Your robots.txt file is blocking search engines access to parts of the website.

  • # MUST be changed to read Disallow: /joomla/administrator/
  • User-agent: *
    • Disallow: /administrator/
    • Disallow: /bin/
    • Disallow: /cache/
    • Disallow: /cli/
    • Disallow: /components/
    • Disallow: /includes/
    • Disallow: /installation/
    • Disallow: /language/
    • Disallow: /layouts/
    • Disallow: /libraries/
    • Disallow: /logs/
    • Disallow: /modules/
    • Disallow: /plugins/
    • Disallow: /tmp/
    • Disallow: /test/
    User-Agent: Googlebot
    • Allow: /*.js*
    • Allow: /*.css*
    A robots.txt file restricts access to search engine robots that crawl the web. (www.robotstxt.org/robotstxt.html)

    XML Sitemap

    SEO
    Found following XML sitemap(s):
    Sitemaps inform search engines about pages available for crawling. In its simplest form, a Sitemap is an XML file that lists URLs for a site along with additional metadata about each URL. XML sitemap should help search engines to crawl the site more intelligently. (www.sitemaps.org/protocol.html)

    Accessibility Check

    accessibility
    WCAG 2.0 (AA) Conformance Test: FAILED [35 error(s)]
    1. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 114, Col 11] <span>CBM Mortgage</span>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    2. i (italic) element used.
      [Line 170, Col 6] <i class="fa fa-bars"></i>
      Replace your i elements with em or strong.
    3. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 873, Col 4] <dt class="article-info-term"> Details</dt>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    4. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 896, Col 5] <h1>Welcome to CBM Mortgage</h1>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    5. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 897, Col 1] <p><br /><strong>CBM Mortgage</strong> is a mortgage financing company devoted to helping you get th ...
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    6. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 897, Col 10] <strong>CBM Mortgage</strong>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    7. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 897, Col 399] <strong>Winchester, VA</strong>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    8. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 898, Col 1] <p>We provide home mortgages, real estate loans &amp; refinancing services.</p>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    9. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 899, Col 1] <p>We take pride in giving our clients the highest quality customer service in the <strong>Shenandoa ...
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    10. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 899, Col 84] <strong>Shenandoah Valley</strong>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    11. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 901, Col 1] <p>Our <a href="/loan-originators" title="Loan Originators">experienced staff</a> will&nbsp;take the ...
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    12. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 902, Col 4] <strong>It is our goal to provide you with everything you need to make an informed decision about yo ...
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    13. Header nesting - header following h2 is incorrect.
      [Line 903, Col 1] <h2>How Do You Choose the Right Mortgage Company?</h2>
      Modify the header levels so only an h3 or any header less than h3 follows h2.
    14. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 904, Col 1] <span style="font-size: 11pt; line-height: 115%; font-family: Calibri, sans-serif;">Let's face it— ...
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    15. i (italic) element used.
      [Line 904, Col 400] <i>is</i>
      Replace your i elements with em or strong.
    16. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 906, Col 1] <h4>Latest Mortgage News Headlines</h4>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    17. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 922, Col 7] <span class="srfrFeedItemDate">Dec 12, 2017 | 14:16 pm</span>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    18. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 924, Col 7] <p> Today I find myself in Florida spending time with American Bancshares. Did you know ...
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    19. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 938, Col 7] <span class="srfrFeedItemDate">Dec 11, 2017 | 14:22 pm</span>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    20. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 940, Col 7] <p> Lenders making tough personnel decisions can&rsquo;t &ldquo;kick the can down the r ...
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    21. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 954, Col 7] <span class="srfrFeedItemDate">Dec 8, 2017 | 14:34 pm</span>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    22. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 956, Col 7] <p> Trio&nbsp;is a lease with an option to purchase that you can use to finance your ne ...
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    23. Header nesting - header following h2 is incorrect.
      [Line 1000, Col 2] <h2>Home Loan Programs</h2>
      Modify the header levels so only an h3 or any header less than h3 follows h2.
    24. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 1023, Col 1] <li>VHDA Loan</li>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    25. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 1027, Col 1] <p>Refinancing</p>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    26. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 1030, Col 1] <p>VA Interest Rate Reduction</p>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    27. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 1040, Col 65] <strong>Shopping around for<br />the best mortgage rates? <br />Ask these 10 questions <br />before ...
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    28. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 1069, Col 35] <strong>Front Royal, VA</strong>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    29. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 1070, Col 1] <div style="text-align: center;">(540) 635-1112</div>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    30. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 1077, Col 35] <strong>Winchester, VA</strong>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    31. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 1078, Col 1] <div style="text-align: center;">(540) 931-0346</div>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    32. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 1085, Col 35] <strong>Strasburg, VA</strong>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    33. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 1086, Col 1] <div style="text-align: center;">(540) 692-1621</div>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    34. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 1101, Col 2] <h3 style="text-align: center;">Licensed in Virginia, West Virginia, and Maryland.</h3>
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    35. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
      [Line 1105, Col 1] <p style="text-align: center;">NMLSR ID #282839 | <a target="_blank" href="http://www.nmlsconsumerac ...
      Use a colour contrast evaluator to determine if text and background colours provide a contrast ratio of 4.5:1 for standard text, or 3:1 for larger text. Change colour codes to produce sufficient contrast. http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head
    Following Web accessibility standards while developing a website can help users with specific needs, such as visually impaired, motor/mobility, auditory, seizures, as well as cognitively and intellectually impaired disabilities. Some of these fixes include general seo applications like Alt tags, Form labels, fixing empty links and adding alternative text. To read more about accessibility guidelines follow this link Web Content Accessibility Guidelines (WCAG) Overview.

    Mobile Rendering

    mobile
    Mobile internet usage has been exceeding PC's since 2014 and growing so it is critical for pages to render correctly on mobile devices.

    Mobile Optimization

    mobileperformanceSEO
    Mobile PageSpeed analyzes webpages and evaluates its performance while providing suggestions on reducing page load times. Google is incorporating website speed in search ranking (www.mattcutts.com/blog/site-speed)

    Mobile Experience

    mobileusability
    Mobile users have now become a critical part of online visits. Making the website mobile friendly is no longer an option but rather necessity. (https://developers.google.com/webmasters/smartphone-sites/)

    Favicon

    usability
    favicon
    file: http://cbmmortgage.com/templates/t3_bs3_blank/favicon.ico
    size: 16px  by  16px
    type: image/x-icon
    The Favicon is a small icon associated with a website. The Favicon is important because it is displayed next to the website's URL in the address bar of the browser as well as in bookmarks and shortcuts.

    Custom 404 Error Page

    usability
    Yes, custom 404 error page detected.
    A 404 is a standard http response code for a resource that cannot be located on the server. Web servers usually return a "404 Not Found" error page for non-existing pages. Unfortunately, these default error pages are very generic and a not very user friendly, therefore, using a custom 404 error page is highly recommended.

    Process of returning http status code "200 OK" for a non-existent page or redirecting users to another url is called soft 404. Soft 404 errors are problematic for search engines and are not advisable. (https://support.google.com/webmasters/answer/181708)

    Printability

    usability
    Great, you are using print-friendly CSS:
    Print-friendly pages are designed to fit on an 8.5"x11" or A4 sheet and usually include only the content of the page, along with source information.

    W3C CSS Validation

    validity
    Status: FAILED [117 error(s)]
    It is recommended to use valid CSS to ensure that the website displays correctly. (W3C CSS Validation Service).

    Indexed Pages

    SEO-Authority
    Estimated number of pages indexed by Google™: about 30
    The higher number of indexed pages the more content search engines can index, which increases overall value of the website.

    Domain Age

    SEO-Authority
    Your domain was registerd for the first time: 7 years, 9 months, 1 day ago.
    Age of the domain is one of the many signals that search engines utilize for ranking. Brand new domains generally have more difficult time to rank high for the first few months.

    Domain Expiration

    SEO-Authority
    Your domain expires in: 2 years, 2 months, 27 days.
    Domain expiration far in to the future is considered a good practice as it promotes confidence in your website, decreases chances of losing domain and in certain cases might help with search engine ranking. (https://www.hover.com/blog/three-reasons-to-renew-your-domain-names-for-five-years/)

    IP Canonicalization

    SEO
    No, your site's IP 207.58.181.42 does not redirect to cbmmortgage.com.
    Some web spiders index websites using IP as well as domain name which can cause duplicate content if there is no IP Canonicalization.

    URL Canonicalization

    SEO
    Yes, both the www.cbmmortgage.com and cbmmortgage.com resolve to the same URL.
    Warning: Current redirect is "HTTP/1.1 303 See other" but it should be "HTTP/1.1 301 Moved Permanently"
    Domain name with WWW and without can be considered as different pages causing duplicate content for search engines. (www.mattcutts.com/blog/seo-advice-url-canonicalization)

    Page Speed

    performanceSEO
    Google Page Speed score: 84% (High)
    Rq. Requests Hst. Hosts LT Load time Html Img Images JS JavaScript CSS F Flash O Other PS Page Size
    55102.84s81.2 KB106.65 KB1.72 MB611.71 KB0 B77.57 KB2.57 MB

    RecommendationImpactDetails
    Avoid landing page redirects
    None
    Your page has no redirects.
      Enable compression
      None
      You have compression enabled.
        Leverage browser caching
        Low
        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:
          Reduce server response time
          Medium
          In our test, your server responded in 0.27 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
            Minify CSS
            Low
            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 3KiB (34% reduction).
              Minify HTML
              Low
              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 1.5KiB (16% reduction).
                Minify JavaScript
                Low
                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 6KiB (28% reduction).
                  Eliminate render-blocking JavaScript and CSS in above-the-fold content
                  Medium
                  Your page has 11 blocking script resources and 15 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:Optimize CSS Delivery of the following:
                      Optimize images
                      Low
                      Properly formatting and compressing images can save many bytes of data.
                        Optimize the following images to reduce their size by 17.4KiB (41% reduction).
                        Prioritize visible content
                        Low
                        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 51% of the final above-the-fold content could be rendered with the full HTML response snapshot:26.

                          PageSpeed analyzes webpages and evaluates its performance while providing suggestions on reducing page load times. Google is now incorporating website speed in search ranking (www.mattcutts.com/blog/site-speed)

                          Server Information

                          security

                          ISP:
                          ServInt
                          Server IP:
                          207.58.181.42
                          Server Location:
                          US VIRGINIA, Reston

                          Name Server 1:
                          ns1.cinric.com (207.58.181.42)
                          Name Server 2:
                          ns2.cinric.com (207.58.181.43)
                          Your server's IP address and location have minor impact on the country specific SEO. It is recommend to host the website in the country where the number of vistors is desired to be the highest. Search engines take the geolocation of a server into account. (www.youtube.com/watch?v=hXt23AXlJJU)

                          HTTPS (SSL)

                          security
                          Issued To:
                          Common Name (CN):
                          cbmmortgage.com
                          Issuer:
                          Common Name (CN):
                          cPanel, Inc. Certification Authority
                          Oranization (O):
                          cPanel, Inc.
                          Period of Validity
                          Begins On:
                          09/17/2017
                          Expires On:
                          12/16/2017
                          Google™ is now treating HTTPS as a ranking signal. HTTPS is a secure web protocol that allows for encrypted communication between website and the client. HTTPS protocol requires your website to have an SSL certificate, which can be purchased from a Certificate Authority (CA) or SSL vendor. (security.googleblog.com/2014/08/https-as-ranking-signal_6.html).

                          Safe Browsing

                          security
                          Yes
                          Safe Browsing is a service provided by Google that enables applications to check URLs against Google's constantly updated lists of suspected phishing and malware pages. If your site is marked as unsafe see our guide on how to fix websites blocked by google safe browsing

                          Spam Blacklist

                          security
                          Good, your IP 207.58.181.42 is not blacklisted.
                          Spammer directories provide lists of IPs from which spam distribution is reported. Emails sent from the blocked IPs are subject to closer scrutiny and are much less likely to be delivered. For email campaigns it is recommended to utilize professional email services to ensure that your website IP is not blocked. (www.stopforumspam.com)

                          Email Address Obfuscation

                          security
                          Great, this webpage does not contain email addresses displayed in plain text.
                          It is recommended to obfuscate email addresses posted in public. This prevents email addresses from being automatically harvested by spam bots which helps to decrease number of unsolicited emails. See our email obfuscation techniques guide for more details.

                          Directory Browsing

                          security
                          Great, your server has directory browsing disabled.
                          Protect Webserver directories from unwanted browsing. To enhance security, directory browsing should be disabled unless you have a specific reason to enable it. If you enable directory browsing, make sure that you only enable it on the particular directory or directories that you want to share. (https://technet.microsoft.com/en-us/library/cc731109)

                          Whois Privacy

                          security
                          Registrant:
                          Name:
                          Cory Michael
                          Whois Privacy is a service that prevents domain owner contact information from being displayed in the publicly available Whois records. This can help to cut down on unwanted spam but utilizing Whois privacy should be evaluated against business model and branding strategy.

                          Server Signature

                          security
                          Good, your server does not provide version information.
                          Attackers can utilize server signature versioning information to their advantage therefore it is recommended to disable it when possible.