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

iwebchk

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. (www.searchenginejournal.com/seo-without-boarders-a-guide-to-international-seo-nick-paterman/60092/)

Images

accessibilitySEO-content
Good, most images have ALT attribute.
Number of images: 18
Missing alt tag: 2

List of images with missing ALT attributes:

  • http://www.sweepachim.com/wp-content/uploads/2016/07/Regency-652x411.png
  • http://www.sweepachim.com/wp-content/uploads/2016/03/CS1200-B-610x340.jpg
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:

"Sweep-A-Chim - Chimney Service Company"

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

"Chimney Service Company"

Length: 23 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
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 23.94%
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>
chimney4.67%451175-
sweep-a-chim1.97%191-33-
stoves1.66%16--42-
home1.25%12-----
masonry1.14%11--31-
service1.04%1011---
regency1.04%10--1--
inspections0.83%8--21-
stove0.83%8--2--
fireplaces0.83%8--11-
masonry repairs0.73%7--3--
chimney inspections0.62%6--2--
chimney service0.52%511---
chimney sweep0.52%5--1--
service company0.42%411---
chimney service company0.42%411---
discounted pre-owned stoves0.21%2--1--
regency prefabricated fireplaces0.21%2-----
them come out0.21%2-----
operated since 19870.10%1--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.
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>
    • Sweep-A-Chim
  • 3 <H2>
    • SWEEP-A-CHIM
    • CHIMNEY INSPECTIONS.CHIMNEY SWEEPS.MASONRY REPAIRS.CHIMNEY RELININGS
    • We are licensed contractors. You can look us up under MHIC #37037
  • 14 <H3>
    • Chimney Inspections
    • Chimney Sweeping
    • Masonry Repairs
    • Chimney Relining
    • Insert Stoves
    • Freestanding Stoves
    • Prefabricated Fireplaces
    • Discounted Pre-Owned Stoves
    • New Homeowner!!
    • Why Choose Regency Brand Stoves?
    • Pellet Stove or Wood Stove… That is the question!
    • Heavy Snow and Masonry Repairs
    • Wood Burning Safety Tips
    • How to Hire a Chimney Sweep
  • 8 <H4>
    • Family owned and operated since 1987
    • All trained and certfied
    • Dave
    • Kyle
    • Kenny
    • We want you to feel apart of the Sweep-A-Chim family. So stay connected with us!
    • Take a look at what our customers think!
    • Shoot us a message below or give us a call at: (410) 679-7959
  • 3 <H5>
    • Founder and Owner
    • Owner
    • General Manager
  • 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-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 [3 errors, 0 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
No web anlytics tools found.
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://sweepachim.com/robots.txt

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

    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 [50 error(s)]
    • Anchor contains no text.
      [Line 151, Col 25] <a target="_blank" href="https://www.facebook.com/sweep.achim"><i class="fa fa-facebook"></i></a>
      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 151, Col 88] <i class="fa fa-facebook"></i>
      Replace your i elements with em or strong.
    • Anchor contains no text.
      [Line 152, Col 29] <a target="_blank" href="https://www.youtube.com/user/sweepachim"><i class="fa fa-youtube"></i></a>
      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 152, Col 95] <i class="fa fa-youtube"></i>
      Replace your i elements with em or strong.
    • Anchor contains no text.
      [Line 153, Col 29] <a target="_blank" href="https://plus.google.com/115415868193968095602"><i class="fa fa-google-plus" ...
      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 153, Col 101] <i class="fa fa-google-plus"></i>
      Replace your i elements with em or strong.
    • Anchor contains no text.
      [Line 154, Col 29] <a target="_blank" href="mailto:info@sweepachim.com"><i class="fa fa-envelope"></i></a>
      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 154, Col 82] <i class="fa fa-envelope"></i>
      Replace your i elements with em or strong.
    • Anchor contains no text.
      [Line 155, Col 33] <a target="_blank" href="tel:+4106797959"><i class="fa fa-phone"></i></a>
      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 155, Col 75] <i class="fa fa-phone"></i>
      Replace your i elements with em or strong.
    • The contrast between the colour of selected link text and its background is not sufficient to meet WCAG2.0 Level AA.
      [Line 178, Col 29] <a class="navbar-brand" href="http://www.sweepachim.com">Sweep-A-Chim</a>
      Use a colour contrast evaluator to determine if selected link 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
    • Anchor contains no text.
      [Line 181, Col 25] <a target="_blank" href="https://www.facebook.com/sweep.achim"><i class="fa fa-facebook"></i></a>
      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 181, Col 88] <i class="fa fa-facebook"></i>
      Replace your i elements with em or strong.
    • Anchor contains no text.
      [Line 182, Col 29] <a target="_blank" href="https://www.youtube.com/user/sweepachim"><i class="fa fa-youtube"></i></a>
      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 182, Col 95] <i class="fa fa-youtube"></i>
      Replace your i elements with em or strong.
    • Anchor contains no text.
      [Line 183, Col 29] <a target="_blank" href="https://plus.google.com/115415868193968095602"><i class="fa fa-google-plus" ...
      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 183, Col 101] <i class="fa fa-google-plus"></i>
      Replace your i elements with em or strong.
    • Anchor contains no text.
      [Line 184, Col 29] <a target="_blank" href="mailto:info@sweepachim.com"><i class="fa fa-envelope"></i></a>
      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 184, Col 82] <i class="fa fa-envelope"></i>
      Replace your i elements with em or strong.
    • Anchor contains no text.
      [Line 185, Col 33] <a target="_blank" href="tel:4106797959"><i class="fa fa-phone"></i></a>
      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 185, Col 74] <i class="fa fa-phone"></i>
      Replace your i elements with em or strong.
    • The contrast between the colour of selected link text and its background is not sufficient to meet WCAG2.0 Level AA.
      [Line 191, Col 280] <a title="Home" href="http://www.sweepachim.com/#Top">Home</a>
      Use a colour contrast evaluator to determine if selected link 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 selected link text and its background is not sufficient to meet WCAG2.0 Level AA.
      [Line 192, Col 158] <a title="Services" href="http://www.sweepachim.com/#ServicesSection">Services</a>
      Use a colour contrast evaluator to determine if selected link 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 selected link text and its background is not sufficient to meet WCAG2.0 Level AA.
      [Line 193, Col 158] <a title="Products" href="http://www.sweepachim.com/#Products">Products</a>
      Use a colour contrast evaluator to determine if selected link 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 selected link text and its background is not sufficient to meet WCAG2.0 Level AA.
      [Line 194, Col 158] <a title="About Us" href="http://www.sweepachim.com/#AboutUs">About Us</a>
      Use a colour contrast evaluator to determine if selected link 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 selected link text and its background is not sufficient to meet WCAG2.0 Level AA.
      [Line 195, Col 158] <a title="Our Team" href="http://www.sweepachim.com/#OurTeam">Our Team</a>
      Use a colour contrast evaluator to determine if selected link 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 selected link text and its background is not sufficient to meet WCAG2.0 Level AA.
      [Line 196, Col 158] <a title="Contact Us" href="http://www.sweepachim.com/#contact">Contact Us</a>
      Use a colour contrast evaluator to determine if selected link 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 selected link text and its background is not sufficient to meet WCAG2.0 Level AA.
      [Line 197, Col 158] <a title="Tips and Tricks" href="http://www.sweepachim.com/#TipsAndTricks">Tips and Tricks</a>
      Use a colour contrast evaluator to determine if selected link 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 selected link text and its background is not sufficient to meet WCAG2.0 Level AA.
      [Line 215, Col 54] <a class="ghost-button-semi-transparent" href="#Services">LEARN MORE</a>
      Use a colour contrast evaluator to determine if selected link 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
    • b (bold) element used.
      [Line 237, Col 5] <b>Level 1</b>
      Replace your b (bold) elements with em or strong.
    • b (bold) element used.
      [Line 238, Col 5] <b>Level 2</b>
      Replace your b (bold) elements with em or strong.
    • b (bold) element used.
      [Line 239, Col 5] <b>Level 3</b>
      Replace your b (bold) elements with em or strong.
    • b (bold) element used.
      [Line 261, Col 546] <b>RELINING</b>
      Replace your b (bold) elements with em or strong.
    • b (bold) element used.
      [Line 261, Col 563] <b>RELINING</b>
      Replace your b (bold) elements with em or strong.
    • The contrast between the colour of selected link text and its background is not sufficient to meet WCAG2.0 Level AA.
      [Line 276, Col 98] <a href="#contactus">Contact Us</a>
      Use a colour contrast evaluator to determine if selected link 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
    • Header nesting - header following h2 is incorrect.
      [Line 351, Col 71] <h2>We are licensed contractors. You can look us up under MHIC #37037</h2>
      Modify the header levels so only an h3 or any header less than h3 follows h2.
    • The contrast between the colour of selected link text and its background is not sufficient to meet WCAG2.0 Level AA.
      [Line 352, Col 98] <a target="_blank" href="https://www.dllr.state.md.us/cgi-bin/ElectronicLicensing/OP_Search/OP_searc ...
      Use a colour contrast evaluator to determine if selected link 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 424, Col 15] <i class="fa fa-facebook"></i>
      Replace your i elements with em or strong.
    • i (italic) element used.
      [Line 434, Col 15] <i class="fa fa-youtube"></i>
      Replace your i elements with em or strong.
    • i (italic) element used.
      [Line 444, Col 15] <i class="fa fa-google-plus"></i>
      Replace your i elements with em or strong.
    • input element, type of "text", missing an associated label.
      [Line 498, Col 65] <input data-sr="wait 0.3s, enter left and move 50px after 1s" type="text" id="myname" name="myname" ...
      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.
    • Label text is empty.
      [Line 498, Col 65] <input data-sr="wait 0.3s, enter left and move 50px after 1s" type="text" id="myname" name="myname" ...
      Add text to the label element.
    • input element, type of "text", has no text in label.
      [Line 498, Col 65] <input data-sr="wait 0.3s, enter left and move 50px after 1s" type="text" id="myname" name="myname" ...
      Add text to the input element's associated label that describes the purpose or function of the control.
    • input element, type of "text", missing an associated label.
      [Line 499, Col 65] <input data-sr="wait 0.3s, enter left and move 50px after 1s" type="text" id="email" name="email" pl ...
      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.
    • Label text is empty.
      [Line 499, Col 65] <input data-sr="wait 0.3s, enter left and move 50px after 1s" type="text" id="email" name="email" pl ...
      Add text to the label element.
    • input element, type of "text", has no text in label.
      [Line 499, Col 65] <input data-sr="wait 0.3s, enter left and move 50px after 1s" type="text" id="email" name="email" pl ...
      Add text to the input element's associated label that describes the purpose or function of the control.
    • input element, type of "text", missing an associated label.
      [Line 500, Col 65] <input data-sr="wait 0.3s, enter left and move 50px after 1s" type="text" id="website" name="website ...
      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.
    • Label text is empty.
      [Line 500, Col 65] <input data-sr="wait 0.3s, enter left and move 50px after 1s" type="text" id="website" name="website ...
      Add text to the label element.
    • input element, type of "text", has no text in label.
      [Line 500, Col 65] <input data-sr="wait 0.3s, enter left and move 50px after 1s" type="text" id="website" name="website ...
      Add text to the input element's associated label that describes the purpose or function of the control.
    • textarea element missing an associated label.
      [Line 503, Col 41] <textarea data-sr="wait 0.3s, enter right and move 50px after 1s" id="comments" name="comments" clas ...
      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.
    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
    Missing
    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
    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 [97 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™: not available
    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: 6 years, 5 months, 17 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.

    Domain Expiration

    SEO-Authority
    Your domain expires in: 3 years, 6 months, 12 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 198.54.116.74 does not redirect to sweepachim.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.sweepachim.com and sweepachim.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: 39% (Low)
    Rq. Requests Hst. Hosts LT Load time Html Img Images JS JavaScript CSS F Flash O Other PS Page Size
    7454.75s57.39 KB2.79 MB454.21 KB458.28 KB0 B154.95 KB3.89 MB

    RecommendationImpactDetails
    Avoid landing page redirects
    None
    Your page has no redirects.
      Enable compression
      None
      You have compression enabled.
        Leverage browser caching
        High
        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
          High
          In our test, your server responded in 0.98 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 6.2KiB (23% reduction).
              Minify HTML
              None
              Your HTML is minified.
                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 2.5KiB (20% reduction).
                  Eliminate render-blocking JavaScript and CSS in above-the-fold content
                  Medium
                  Your page has 2 blocking script resources and 17 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 1.3MiB (52% 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 (www.mattcutts.com/blog/site-speed)

                          Server Information

                          security

                          ISP:
                          Namecheap
                          Server IP:
                          198.54.116.74
                          Server Location:
                          US CALIFORNIA, Los Angeles

                          Name Server 1:
                          dns1.namecheaphosting.com (216.87.155.33)
                          Name Server 2:
                          dns2.namecheaphosting.com (216.87.152.33)
                          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):
                          *.web-hosting.com
                          Issuer:
                          Common Name (CN):
                          COMODO RSA Domain Validation Secure Server CA
                          Oranization (O):
                          COMODO CA Limited
                          Period of Validity
                          Begins On:
                          02/03/2015
                          Expires On:
                          03/07/2018

                          Warning: The SSL certificate is invalid for sweepachim.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. (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 198.54.116.74 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:
                          • info@sweepachim.com
                          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
                          No contact information available.
                          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 PHP/5.4.45
                          Attackers can utilize server signature versioning information to their advantage therefore it is recommended to disable it when possible.