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 wynneplumbing.com

iwebchk

  • screenshot of wynneplumbing.com
  • Score:

    59.6%

    3.38
    Progress:
    100%
    Generated on Tuesday, July 4th 2017 4:24 pm
    07/04/2017

Top Priorities

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

Traffic Rank

visitors
No Data available. (very low)
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. (http://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: 6
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:

"Home - Wynne Plumbing & Heating Co."

Length: 35 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:

"Family owned and operated since 1965, Wynne Plumbing & Heating has served New York City with exceptional plumbing and heating services for over 40 years."

Length: 153 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. (en.wikipedia.org/wiki/Meta_element#The_description_attribute)

Keywords Metatag

SEO-content
No Keywords Found.
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 3.66%
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>
plumbing7.21%151213-
heating4.81%10121--
wynne4.81%101122-
services3.37%7-11--
new2.40%5-1-1-
city2.40%5-1-1-
york2.40%5-1-1-
contact1.92%4--1--
service1.92%4---11
7181.92%4-----
wynne plumbing4.33%9111--
new york2.40%5-1---
york city1.92%4-1---
operated since0.96%2-1---
since 19650.96%2-1---
new york city1.92%4-1---
served new york0.96%2-1---
operated since 19650.96%2-1---
proudly served new0.48%1-----
commercial customers choose0.48%1-----

Warning: Keywords density of above 5% might have negative impact on search engine listing

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 5% is a good indication that the word or 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>
    • Wynne Plumbing & Heating Co.
  • 3 <H2>
    • History of Wynne
    • Our Services
    • Contact Us
  • 0 <H3>
  • 0 <H4>
  • 4 <H5>
    • WHO WE ARE
    • ADDRESS
    • PHONE
    • HOURS
  • 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 (en.wikipedia.org/wiki/Character_encodings_in_HTML).

Language

usability
Declared Language: en-US (English)
Language Attribute: en-US (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 [4 errors, 4 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. (webdesign.about.com/od/htmltags/a/bltags_deprctag.htm)

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://www.wynneplumbing.com/robots.txt

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

User-agent: *
  • Disallow: /wp-admin/
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. (http://www.sitemaps.org/protocol.html)

Accessibility Check

accessibility
WCAG 2.0 (AA) Conformance Test: FAILED [44 error(s)]
  • i (italic) element used.
    [Line 230, Col 152] <i class="x-icon-facebook-square" data-x-icon="&#xf082;" aria-hidden="true"></i>
    Replace your i elements with em or strong.
  • Header nesting - header following h1 is incorrect.
    [Line 236, Col 1] <h1 class="visually-hidden">Wynne Plumbing &amp; Heating Co.</h1>
    Modify the header levels so only an h1 or h2 follows h1.
  • i (italic) element used.
    [Line 240, Col 1] <i class="x-icon-bars" data-x-icon="&#xf0c9;"></i>
    Replace your i elements with em or strong.
  • i (italic) element used.
    [Line 249, Col 111] <i class="_mi _before dashicons dashicons-phone" aria-hidden="true"></i>
    Replace your i elements with em or strong.
  • i (italic) element used.
    [Line 257, Col 92] <i class="_mi _before dashicons dashicons-phone" aria-hidden="true"></i>
    Replace your i elements with em or strong.
  • Anchor contains no text.
    [Line 269, Col 1] <a href="#" class="x-slider-scroll-bottom below top left"> <i class="x-icon-angle-down" data-x-icon= ...
    Add text to the a element or the title attribute of the a element or, if an image is used within the anchor, add Alt text to the image.
  • i (italic) element used.
    [Line 270, Col 1] <i class="x-icon-angle-down" data-x-icon="&#xf107;" aria-hidden="true"></i>
    Replace your i elements with em or strong.
  • i (italic) element used.
    [Line 319, Col 405] <i class="fa-icon-chevron-right"></i>
    Replace your i elements with em or strong.
  • The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 443, Col 1099] <span>Our Services</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
  • The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 443, Col 1177] <p>Wynne Plumbing and Heating offers a variety of services to meet the needs of your business. Our e ...
    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
  • The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 444, Col 105] <li class="x-li-icon" ><i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" >< ...
    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
  • i (italic) element used.
    [Line 444, Col 132] <i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" ></i>
    Replace your i elements with em or strong.
  • The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 444, Col 228] <li class="x-li-icon" ><i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" >< ...
    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
  • i (italic) element used.
    [Line 444, Col 255] <i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" ></i>
    Replace your i elements with em or strong.
  • The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 444, Col 378] <li class="x-li-icon" ><i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" >< ...
    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
  • i (italic) element used.
    [Line 444, Col 405] <i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" ></i>
    Replace your i elements with em or strong.
  • The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 444, Col 513] <li class="x-li-icon" ><i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" >< ...
    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
  • i (italic) element used.
    [Line 444, Col 540] <i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" ></i>
    Replace your i elements with em or strong.
  • The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 444, Col 626] <li class="x-li-icon" ><i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" >< ...
    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
  • i (italic) element used.
    [Line 444, Col 653] <i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" ></i>
    Replace your i elements with em or strong.
  • The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 444, Col 753] <li class="x-li-icon" ><i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" >< ...
    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
  • i (italic) element used.
    [Line 444, Col 780] <i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" ></i>
    Replace your i elements with em or strong.
  • The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 444, Col 907] <li class="x-li-icon" ><i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" >< ...
    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
  • i (italic) element used.
    [Line 444, Col 934] <i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" ></i>
    Replace your i elements with em or strong.
  • The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 444, Col 1035] <li class="x-li-icon" ><i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" >< ...
    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
  • i (italic) element used.
    [Line 444, Col 1062] <i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" ></i>
    Replace your i elements with em or strong.
  • The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 444, Col 1151] <li class="x-li-icon" ><i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" >< ...
    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
  • i (italic) element used.
    [Line 444, Col 1178] <i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" ></i>
    Replace your i elements with em or strong.
  • The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 444, Col 1291] <li class="x-li-icon" ><i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" >< ...
    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
  • i (italic) element used.
    [Line 444, Col 1318] <i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" ></i>
    Replace your i elements with em or strong.
  • The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 444, Col 1447] <li class="x-li-icon" ><i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" >< ...
    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
  • i (italic) element used.
    [Line 444, Col 1474] <i class="x-icon-check" data-x-icon="&#xf00c;" aria-hidden="true" ></i>
    Replace your i elements with em or strong.
  • Header nesting - header following h2 is incorrect.
    [Line 444, Col 2289] <h2 class="h-custom-headline h3" style="margin-top:0em !important;"><span>Contact Us</span></h2>
    Modify the header levels so only an h3 or any header less than h3 follows h2.
  • Label text is empty.
    [Line 463, Col 49] <input type="text" name="your-name" value="" size="40" class="wpcf7-form-control wpcf7-text wpcf7-va ...
    Add text to the label element.
  • input element, type of "text", missing an associated label.
    [Line 463, Col 49] <input type="text" name="your-name" value="" size="40" class="wpcf7-form-control wpcf7-text wpcf7-va ...
    Add a label element that surrounds the control's label. Set the for attribute on the label element to the same value as the id attribute of the control. And/or add a title attribute to the input element. And/or create a label element that contains the input element.
  • input element, type of "text", has no text in label.
    [Line 463, Col 49] <input type="text" name="your-name" value="" size="40" class="wpcf7-form-control wpcf7-text wpcf7-va ...
    Add text to the input element's associated label that describes the purpose or function of the control.
  • Label text is empty.
    [Line 465, Col 50] <input type="email" name="your-email" value="" size="40" class="wpcf7-form-control wpcf7-text wpcf7- ...
    Add text to the label element.
  • Label text is empty.
    [Line 467, Col 47] <input type="tel" name="tel-998" value="" size="40" class="wpcf7-form-control wpcf7-text wpcf7-tel w ...
    Add text to the label element.
  • textarea element missing an associated label.
    [Line 469, Col 52] <textarea name="your-message" cols="40" rows="10" class="wpcf7-form-control wpcf7-textarea" aria-inv ...
    Add a label element immediately before or after the textarea element. Set the for attribute value of the label element to the same value as the id attribute value of the textarea element. Add label text to the label element. Or, set the title attribute value to the textarea element to the label text. Or, add a label element that surrounds the textarea element and add label text.
  • textarea element missing an associated label.
    [Line 479, Col 1] <textarea id="g-recaptcha-response" name="g-recaptcha-response" class="g-recaptcha-response" style=" ...
    Add a label element immediately before or after the textarea element. Set the for attribute value of the label element to the same value as the id attribute value of the textarea element. Add label text to the label element. Or, set the title attribute value to the textarea element to the label text. Or, add a label element that surrounds the textarea element and add label text.
  • i (italic) element used.
    [Line 496, Col 152] <i class="x-icon-facebook-square" data-x-icon="&#xf082;" aria-hidden="true"></i>
    Replace your i elements with em or strong.
  • The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 497, Col 1] <div class="x-colophon-content"> Copyright 2015 Wynne Plumbing & Heating Co. <p>DESIGNED BY <a href= ...
    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
  • The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 499, Col 1] <p>DESIGNED BY <a href="http://www.ucsaintl.com" title="UCSA International" target="_blank">UCSA Int ...
    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
  • i (italic) element used.
    [Line 504, Col 1] <i class="x-icon-angle-up" data-x-icon="&#xf106;"></i>
    Replace your i elements with em or strong.
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 (http://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

Warning: favicon dimensions are incorrect. Recommended sizes are 16x16, 32x32, 48x48 and 64x64 px

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. (en.wikipedia.org/wiki/Favicon)

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. Webservers 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
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. (webdesign.about.com/od/printerfriendly/a/aa041403a.htm)

W3C CSS Validation

validity
Status: FAILED [84 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 10
The higher number of indexed pages the more content search engines can index, which increases overall value of the website. (en.wikipedia.org/wiki/Search_engine_indexing)

Domain Age

SEO-Authority
Your domain was registerd for the first time: 11 years, 3 months, 25 days 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. (http://www.coconutheadphones.com/does-domain-agematter)

Domain Expiration

SEO-Authority
Your domain expires in: 2 years, 5 months, 25 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 107.180.51.203 does not redirect to wynneplumbing.com.
Some web spiders index websites using IP as well as domain name which can cause duplicate content if there is no IP Canonicalization. (www.mattcutts.com/blog/seo-advice-url-canonicalization)

URL Canonicalization

SEO
Yes, both the www.wynneplumbing.com and wynneplumbing.com resolve to the same URL.
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: 60% (Average)
Rq. Requests Hst. Hosts LT Load time Html Img Images JS JavaScript CSS F Flash O Other PS Page Size
5182.02s80.72 KB1.77 MB1.05 MB437.09 KB0 B296.74 KB3.62 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
        None
        Your server responded quickly.
          Minify CSS
          None
          Your CSS is minified.
            Minify HTML
            None
            Your HTML is minified.
              Minify JavaScript
              None
              Your JavaScript content is minified.
                Eliminate render-blocking JavaScript and CSS in above-the-fold content
                High
                Your page has 1 blocking script resources and 3 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
                    High
                    Properly formatting and compressing images can save many bytes of data.
                      Optimize the following images to reduce their size by 584.5KiB (71% reduction).
                      Prioritize visible content
                      None
                      You have the above-the-fold content properly prioritized.

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

                        Server Information

                        security

                        ISP:
                        GoDaddy.com, LLC
                        Server IP:
                        107.180.51.203
                        Server Location:
                        US ARIZONA, Scottsdale

                        Name Server 1:
                        ns11.domaincontrol.com (216.69.185.6)
                        Name Server 2:
                        ns12.domaincontrol.com (208.109.255.6)
                        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. (http://www.youtube.com/watch?v=hXt23AXlJJU)

                        HTTPS (SSL)

                        security
                        Issued To:
                        Common Name (CN):
                        *.prod.iad2.secureserver.net
                        Issuer:
                        Common Name (CN):
                        Starfield Secure Certificate Authority - G2
                        Oranization (O):
                        Starfield Technologies, Inc.
                        Oranizational Unit (OU):
                        http://certs.starfieldtech.com/repository/
                        Period of Validity
                        Begins On:
                        01/20/2015
                        Expires On:
                        01/20/2018

                        Warning: The SSL certificate is invalid for wynneplumbing.com domain.
                        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. (http://googleonlinesecurity.blogspot.in/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 107.180.51.203 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
                        There is 1 email in plain text on the webpage:
                        • [email protected]
                        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. (http://technet.microsoft.com/en-us/library/cc731109)

                        Whois Privacy

                        security
                        Registrant:
                        Name:
                        Registration Private
                        Organization:
                        Domains By Proxy, LLC
                        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
                        On, Apache/2.4.25
                        Attackers can utilize server signature versioning information to their advantage therefore it is recommended to disable it when possible. (Disable server signature for Apache or IIS).