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 janet.seo-copy.co.uk

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
Perfect, all images have ALT attribute.
Number of images: 15
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:

"Supported Holidays | Adult Learning Disabilities | Chrysalis Holidays"

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

"Chrysalis supported holidays for adults with learning disabilities. Holiday support for special needs & disability supported holidays, UK & abroad."

Length: 147 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 10.28%
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>
holidays5.37%442248-
supported2.93%241235-
holiday2.56%21-173-
care1.71%14--22-
chrysalis1.59%1311-1-
learning0.98%8112--
activities0.98%8--1--
england0.98%8-----
types0.85%7--33-
destinations0.85%7--31-
supported holidays2.80%23123--
chrysalis holidays0.98%81----
holiday destinations0.73%6--3--
holiday themes0.61%5--2--
learning disabilities0.49%4111--
care quality commission0.37%3--1--
read more here0.37%3-----
individual supported holidays0.37%3-----
england north west0.24%2-----
north east england0.24%2-----
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>
    • Providing Supported Holidays Since 1991
  • 3 <H2>
    • Holiday Destinations
    • Holiday Themes
    • Holiday Types Types
  • 3 <H3>
    • New York
    • £2560
    • Route
  • 16 <H4>
    • Supported Holidays for People With Learning Disabilities
    • Click on any of the following headings to find out more
    • Our Supported Holidays
    • What holidays are available
    • Care & Keyworkers
    • Home Visits
    • Transport
    • Behind the Scenes
    • Ethos Behind Our Learning Disability Activities
    • Featured Holiday Destinations & Packages
    • 2017 Brochure
    • Regulated by Care Quality Commission
    • Our Location
    • Holiday Destinations
    • Holiday Themes
    • Holiday Types
  • 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 [13 errors, 8 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://www.janet.seo-copy.co.uk/robots.txt

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

User-agent: *
  • Disallow: /wp-admin/
  • Allow: /wp-admin/admin-ajax.php
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 [64 error(s)]
  1. Anchor contains no text.
    [Line 131, Col 357] <a href="http://www.janet.seo-copy.co.uk/"></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.
  2. Header nesting - header following h1 is incorrect.
    [Line 137, Col 24] <h1 class="header-text">Providing Supported Holidays Since 1991</h1>
    Modify the header levels so only an h1 or h2 follows h1.
  3. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 142, Col 378] <span itemprop="name">Home</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
  4. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 144, Col 169] <span itemprop="name">About</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
  5. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 147, Col 205] <span itemprop="name">Holidays</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
  6. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 149, Col 207] <span itemprop="name">Holiday Destinations</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
  7. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 151, Col 203] <span itemprop="name">Canary Islands</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
  8. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 152, Col 207] <span itemprop="name">Continental Europe</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
  9. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 153, Col 207] <span itemprop="name">England North West</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
  10. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 154, Col 196] <span itemprop="name">Ireland</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
  11. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 155, Col 202] <span itemprop="name">Lake District</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
  12. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 156, Col 202] <span itemprop="name">Mediterranean</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
  13. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 157, Col 200] <span itemprop="name">Scarborough</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
  14. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 158, Col 220] <span itemprop="name">Scotland and North East England</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
  15. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 159, Col 205] <span itemprop="name">South of England</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
  16. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 160, Col 194] <span itemprop="name">Wales</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
  17. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 163, Col 201] <span itemprop="name">Holiday Themes</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 165, Col 192] <span itemprop="name">Adventure</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
  19. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 166, Col 194] <span itemprop="name">Arts &#038; Crafts</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 167, Col 192] <span itemprop="name">Christmas</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
  21. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 168, Col 196] <span itemprop="name">Entertainment</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 169, Col 195] <span itemprop="name">Nature Theme</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
  23. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 170, Col 193] <span itemprop="name">Relaxation</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
  24. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 171, Col 195] <span itemprop="name">Sports Theme</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
  25. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 172, Col 193] <span itemprop="name">Summer Sun</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
  26. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 173, Col 198] <span itemprop="name">Transport Theme</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
  27. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 174, Col 193] <span itemprop="name">Winter Sun</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
  28. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 177, Col 200] <span itemprop="name">Holiday Types</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
  29. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 179, Col 186] <span itemprop="name">Abroad</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
  30. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 180, Col 203] <span itemprop="name">Advanced Care</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
  31. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 181, Col 196] <span itemprop="name">Choice</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
  32. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 182, Col 195] <span itemprop="name">Group</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
  33. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 183, Col 200] <span itemprop="name">Individual</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
  34. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 186, Col 203] <span itemprop="name">Canary Islands</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
  35. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 187, Col 207] <span itemprop="name">Continental Europe</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
  36. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 188, Col 207] <span itemprop="name">England North West</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
  37. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 189, Col 196] <span itemprop="name">Ireland</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
  38. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 190, Col 202] <span itemprop="name">Lake District</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
  39. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 191, Col 202] <span itemprop="name">Mediterranean</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
  40. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 192, Col 200] <span itemprop="name">Scarborough</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
  41. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 193, Col 220] <span itemprop="name">Scotland and North East England</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
  42. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 194, Col 205] <span itemprop="name">South of England</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
  43. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 195, Col 192] <span itemprop="name">USA</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
  44. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 196, Col 194] <span itemprop="name">Wales</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
  45. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 199, Col 177] <span itemprop="name">Meet the Team</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
  46. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 200, Col 168] <span itemprop="name">FAQs</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
  47. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 201, Col 173] <span itemprop="name">Resources</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
  48. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 202, Col 174] <span itemprop="name">Feedback</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
  49. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 203, Col 176] <span itemprop="name">Work With Us</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
  50. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 204, Col 171] <span itemprop="name">Contact</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
  51. Label text is empty.
    [Line 495, Col 701] <input type="text" size="20" id="origin" value="" />
    Add text to the label element.
  52. input element, type of "text", missing an associated label.
    [Line 495, Col 701] <input type="text" size="20" id="origin" value="" />
    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.
  53. input element, type of "text", has no text in label.
    [Line 495, Col 701] <input type="text" size="20" id="origin" value="" />
    Add text to the input element's associated label that describes the purpose or function of the control.
  54. The contrast between the colour of text and its background for the element is not sufficient to meet WCAG2.0 Level AA.
    [Line 496, Col 778] <span itemprop="telephone">01925 220179</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
  55. Header nesting - header following h2 is incorrect.
    [Line 508, Col 439] <h2 class="entry-title" itemprop="name"><a href="http://www.janet.seo-copy.co.uk/holiday-destination ...
    Modify the header levels so only an h3 or any header less than h3 follows h2.
  56. The contrast between the colour of selected link text and its background is not sufficient to meet WCAG2.0 Level AA.
    [Line 508, Col 479] <a href="http://www.janet.seo-copy.co.uk/holiday-destinations/">Holiday Destinations</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
  57. Header nesting - header following h2 is incorrect.
    [Line 511, Col 421] <h2 class="entry-title" itemprop="name"><a href="http://www.janet.seo-copy.co.uk/holiday-themes/">Ho ...
    Modify the header levels so only an h3 or any header less than h3 follows h2.
  58. The contrast between the colour of selected link text and its background is not sufficient to meet WCAG2.0 Level AA.
    [Line 511, Col 461] <a href="http://www.janet.seo-copy.co.uk/holiday-themes/">Holiday Themes</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
  59. The contrast between the colour of selected link text and its background is not sufficient to meet WCAG2.0 Level AA.
    [Line 514, Col 847] <a href="http://www.janet.seo-copy.co.uk/holiday-types/">Holiday Types<p class='ctp-wud-title' style ...
    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
  60. The contrast between the colour of selected link text and its background is not sufficient to meet WCAG2.0 Level AA.
    [Line 514, Col 1110] <a href="http://www.janet.seo-copy.co.uk/categories/types/" rel="tag">Types</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
  61. The contrast between the colour of selected link text and its background is not sufficient to meet WCAG2.0 Level AA.
    [Line 515, Col 147] <a href="/">Chrysalis Holidays</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
  62. The contrast between the colour of selected link text and its background is not sufficient to meet WCAG2.0 Level AA.
    [Line 515, Col 182] <a href="http://www.janet.seo-copy.co.uk/supported-holidays/destinations/">Supported Holidays for Ad ...
    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
  63. The contrast between the colour of selected link text and its background is not sufficient to meet WCAG2.0 Level AA.
    [Line 515, Col 293] <a href="http://www.seo-copy.co.uk/web-blog-design" title="Google Friendly Web Design" target="_blan ...
    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
  64. The contrast between the colour of selected link text and its background is not sufficient to meet WCAG2.0 Level AA.
    [Line 515, Col 421] <a href="http://www.seo-copy.co.uk" target="_blank">SEO Copy</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
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
Subscribe for mobile rendering
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
Subscribe for mobile optimization
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
Subscribe for more details
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://www.janet.seo-copy.co.uk/wp-conte...is-Holidays-supported-holidays-32x32.jpg
size: 32px  by  32px
type: image/jpeg
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
Could not locate 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 [57 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.

Domain Age

SEO-Authority
Your domain was registerd for the first time: 8 years, 1 month, 16 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: 2 years, 10 months, 14 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 213.129.84.167 does not redirect to janet.seo-copy.co.uk.
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.janet.seo-copy.co.uk and janet.seo-copy.co.uk 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: 83% (High)
Rq. Requests Hst. Hosts LT Load time Html Img Images JS JavaScript CSS F Flash O Other PS Page Size
9193.50s76.22 KB876.2 KB1.42 MB265.25 KB0 B192.17 KB2.8 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
              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 20.2KiB (38% reduction).
                Eliminate render-blocking JavaScript and CSS in above-the-fold content
                High
                Your page has 3 blocking script resources and 5 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 6.5KiB (19% 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:
                        The Bunker Secure Hosting Ltd
                        Server IP:
                        213.129.84.167
                        Server Location:
                        GB ENGLAND, London

                        Name Server 1:
                        erin.ns.cloudflare.com (173.245.58.113)
                        Name Server 2:
                        max.ns.cloudflare.com (173.245.59.132)
                        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):
                        titan.solardns.com
                        Issuer:
                        Common Name (CN):
                        cPanel, Inc. Certification Authority
                        Oranization (O):
                        cPanel, Inc.
                        Period of Validity
                        Begins On:
                        03/10/2017
                        Expires On:
                        03/11/2018

                        Warning: The SSL certificate is invalid for janet.seo-copy.co.uk 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 213.129.84.167 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:
                        Organization:
                        Graham Parker
                        Type:
                        UK Individual
                        Address:
                        The registrant is a non-trading individual who has opted to have their, address omitted from the WHOIS service., Data validation:, Nominet was able to match the registrant's name and address against a 3rd party data source on 10-Dec-2012
                        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.