Google recommends separating keywords in URLs by dashes instead of underscores.
Line 1 Google
Dashes perform better than underscores in Google as keyword separators, and underscores perform better than no separators.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:fb="http://www.facebook.com/2008/fbml">
<head>
<title> Takeaways in Fulham, Parson's Green SW6 | hungryhouse</title><base href="http://hungryhouse.co.uk/" /><meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="description" content="Order takeaway online. Find takeaways and restaurants that deliver your favourite food to Fulham and Parson's Green SW6. Pay online or with cash." />
<link href="http://static.hungryhouse.co.uk/css/web-rest.css?30" rel="stylesheet" type="text/css" />
<link href="http://static.hungryhouse.co.uk/css/styles.css?30" rel="stylesheet" type="text/css"/><link rel="stylesheet" type="text/css" href="http://static.hungryhouse.co.uk/css/jquery.uniform.css?30" /><link rel="stylesheet" type="text/css" href="http://static.hungryhouse.co.uk/css/jquery.fancybox.css?30" />
<script type="text/javascript">
var $_hh = {base: "http://hungryhouse.co.uk/",self: "http://hungryhouse.co.uk//include/",aflag: 0,mobile_version: 'http://hungryhouse.co.uk/~m',host: ".hungryhouse.co.uk",media_path: "http://static.hungryhouse.co.uk/",iswl: false};
</script>
<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.8.1/jquery.min.js
"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.tools.min.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.cookie.min.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.history.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.fancybox.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.uniform.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/checkout.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.growl.min.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.easing.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/device.detect.js?30"></script>
Required attribute "type" not specified.
Line 13 HTML Validation
"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.tools.min.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.cookie.min.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.history.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.fancybox.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.uniform.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/checkout.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.growl.min.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.easing.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/device.detect.js?30"></script>
<script language="javascript" src="http://static.hungryhouse.co.uk/include/../css/search/jquery-ui-1.8.9.custom.min.js?30" type="text/javascript"></script><script language="javascript" src="http://static.hungryhouse.co.uk/include/../css/search/restaurants.js?30" type="text/javascript"></script><script language="javascript" src="http://static.hungryhouse.co.uk/include/popup.js?30" type="text/javascript"></script>
<!-- BEGIN:tracking codes top header -->
<meta name="google-site-verification" content="nwWaw9lDdJSi_YeTbtqC6GAdBQ7vG_g3iOGZp1yMJuQ" /><!-- Start Visual Website Optimizer Asynchronous Code -->
<script type='text/javascript'>
var _vwo_code=(function(){
var account_id=6352,
settings_tolerance=2000,
library_tolerance=1500,
use_existing_jquery=false,
// DO NOT EDIT BELOW THIS LINE
f=false,d=document;return{use_existing_jquery:function(){return use_existing_jquery;},library_tolerance:function(){return library_tolerance;},finish:function(){if(!f){f=true;var a=d.getElementById('_vis_opt_path_hides');if(a)a.parentNode.removeChild(a);}},finished:function(){return f;},load:function(a){var b=d.createElement('script');b.src=a;b.type='text/javascript';b.innerText;b.onerror=function(){_vwo_code.finish();};d.getElementsByTagName('head')[0].appendChild(b);},init:function(){settings_timer=setTimeout('_vwo_code.finish()',settings_tolerance);this.load('//dev.visualwebsiteoptimizer.com/j.php?a='+account_id+'
&
u='+encodeURIComponent(d.URL)+'
&
r='+Math.random());var a=d.createElement('style'),b='body{opacity:0 !important;filter:alpha(opacity=0) !important;background:none !important;}',h=d.getElementsByTagName('head')[0];a.setAttribute('id','_vis_opt_path_hides');a.setAttribute('type','text/css');if(a.styleSheet)a.styleSheet.cssText=b;else a.appendChild(d.createTextNode(b));h.appendChild(a);return settings_timer;}};}());_vwo_settings_timer=_vwo_code.init();
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
In HTML the ampersand character (&) is reserved for marking character entities
so you should never use raw ampersands in HTML - including ampersands inside URLs.
For example, any URL that needs an ampersand should look like:
http://www.example.com/file.html?var1=val1&var2=val2&var3=val3
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
In HTML the ampersand character (&) is reserved for marking character entities
so you should never use raw ampersands in HTML - including ampersands inside URLs.
For example, any URL that needs an ampersand should look like:
http://www.example.com/file.html?var1=val1&var2=val2&var3=val3
&
Reference not terminated by REFC delimiter.
Line 24 HTML Validation
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
In HTML the ampersand character (&) is reserved for marking character entities
so you should never use raw ampersands in HTML - including ampersands inside URLs.
For example, any URL that needs an ampersand should look like:
http://www.example.com/file.html?var1=val1&var2=val2&var3=val3
u='+encodeURIComponent(d.URL)+'
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
In HTML the ampersand character (&) is reserved for marking character entities
so you should never use raw ampersands in HTML - including ampersands inside URLs.
For example, any URL that needs an ampersand should look like:
http://www.example.com/file.html?var1=val1&var2=val2&var3=val3
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
In HTML the ampersand character (&) is reserved for marking character entities
so you should never use raw ampersands in HTML - including ampersands inside URLs.
For example, any URL that needs an ampersand should look like:
http://www.example.com/file.html?var1=val1&var2=val2&var3=val3
&
Reference not terminated by REFC delimiter.
Line 24 HTML Validation
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
In HTML the ampersand character (&) is reserved for marking character entities
so you should never use raw ampersands in HTML - including ampersands inside URLs.
For example, any URL that needs an ampersand should look like:
http://www.example.com/file.html?var1=val1&var2=val2&var3=val3
r='+Math.random());var a=d.createElement('style'),b='body{opacity:0 !important;filter:alpha(opacity=0) !important;background:none !important;}',h=d.getElementsByTagName('head')[0];a.setAttribute('id','_vis_opt_path_hides');a.setAttribute('type','text/css');if(a.styleSheet)a.styleSheet.cssText=b;else a.appendChild(d.createTextNode(b));h.appendChild(a);return settings_timer;}};}());_vwo_settings_timer=_vwo_code.init();
</script>
<!-- End Visual Website Optimizer Asynchronous Code --><!-- END:tracking codes top header -->
<link rel="canonical" href="http://hungryhouse.co.uk/takeaways/fulham-parsons-green-sw6"/>
</head>
<body class="bodyRestaurants bodyHungryhouse" id="body_website">
<!-- BEGIN:tracking codes body top -->
<!-- END:tracking codes body top -->
<!-- ClickTaleExcludeBlock -->
<div id="overDiv" style="position:absolute; visibility:hidden; z-index:1000;"></div>
<!-- EndClickTaleExcludeBlock -->
<div class="body">
<div class="topArea">
<div class="header">
This link is broken. The SRC or HREF is an empty string.
Line 46 Broken Link
HREF="" or SRC="" can cause unexpected effects such as traffic spikes or cookie corruption.
<a class="logo" href="" title="order takeaway online">
<span>Hungryhouse.co.uk</span>
</a>
<div class="userInfo">
<a id="mainmenu-item-join" href="/join" id
="guest-join-button" class="toolTipPopup guestJoinButton"><span>Join</span></a>
Duplicate specification of attribute "id".
Line 52 HTML Validation
="guest-join-button" class="toolTipPopup guestJoinButton"><span>Join</span></a>
<span class="tooltipPopup"><
p>Members benefit from a better Checkout experience, but it's also possible to order as a guest without creating an account.</p></span>
Document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag.
Line 53 HTML Validation
p>Members benefit from a better Checkout experience, but it's also possible to order as a guest without creating an account.</p></span>
The A NAME attribute is deprecated in XHTML 1.0, and is illegal in XHTML 1.1 Strict.
Line 55 W3C Deprecated
Use the ID attribute instead.
<a href="/?signin=yes" name="signin" id="guest-login-button" rel="#sign-in-popup-wrapper"><span>Sign in</span></a>
</div>
<ul class="mainNav">
<li class="nav-home">
<a href="/"><span>Home</span></a>
</li>
<li class="active">
<a title="My Order" href="/search_loading"><span>My Order</span></a>
</li>
<li>
<a title="Help" href="/contact"><span>Contact/Help</span></a>
</li>
<li>
<a title="Order Tracking" href="/ordertracking" class="homeNavOrderTracking"><span>Order Tracking</span></a>
</li>
</ul>
<div id="header-message" class="larger">
<span>Order Takeaway Online!</span>
</div>
<scrip
t>try{$(".guestJoinButton").tooltip({ position: ['bottom', 'center'], offset: [14, 0]})} catch(e){}</script>
Required attribute "type" not specified.
Line 75 HTML Validation
t>try{$(".guestJoinButton").tooltip({ position: ['bottom', 'center'], offset: [14, 0]})} catch(e){}</script>
</div>
</div>
<div id="main-container">
<!-- wrapper -->
<!-- /wrapper -->
<div id="maincontent-start"></div>
<!-- Start body -->
<div id="maincontent"> <div class="searchTopArea">
<form action="http://hungryhouse.co.uk/restaurants" method="post" id="search-form">
<div class="searchBar">
<div class="searchBox">
<span class="question">What are you hungry for?</span>
<div class="searchLayout">
<input type="hidden" name="s[p]" value="SW6"/>
This form control has no associated LABEL element.
Add a LABEL tag with the FOR attribute set to the ID of this control. This allows screen readers to tell the user what each control does.
Do not wrap LABEL tags around input controls (implicit labels) since this is very unreliable in older screen readers.
<input type="text" name="s[q]" value="" id="search-suggest" placeholder
There is no attribute "placeholder".
Line 97 HTML Validation
This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen
if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions.
For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes
which were present in earlier versions of HTML.
="Dish name, Restaurant Name..." class="searchInput"/>
<input class="searchButton" type="submit" value="Search"/>
</div>
</div>
<div class="myLocations">
<div class="myLocationLabels">
<i class="icon-searchinfo"></i>
<span class="myPostcodeLabel">My postcode:</span>
<span class="myLocationsCurrentPostcode">SW6</span>
</div>
<div class="shopping-cart-location-border" id="shopping-cart-location-border">
This form control has no associated LABEL element.
Add a LABEL tag with the FOR attribute set to the ID of this control. This allows screen readers to tell the user what each control does.
Do not wrap LABEL tags around input controls (implicit labels) since this is very unreliable in older screen readers.
This form has fields without LABEL elements or TITLE attributes.
Line 108 Section 508 1194.22 (n)
Screen readers use LABEL elements or TITLE attributes to describe form fields to non-sighted users.
Without these, forms are very hard to use with a screen reader.
Forms designed to be completed online shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
Use LABEL tags for each data entry field to show what data is expected.
Line 108 Usability.gov 13:5
Make sure each INPUT field has an associated LABEL tag describing the field.
<input type="text" name="s[p]" value="SW6" class="restsInputItem" id="postcode-field"/>
<button class="restsInputItem" id="change-location-button" type="submit"><span>Go</span></button>
</div>
<a href="javascript:;" id="change-location-link"><span>Change location</span></a>
</div>
</div>
<br class="clear"/>
</form>
</div>
<div class="bodyContent" id="body-content">
<div class="colLeft">
<div class="cuisines restsFilterBoxCuisines">
<h3>Cuisines</h3>
<ul>
<li class="">
<label><a><span>All Cuisines</span></a></label></li>
LABEL elements should be associated with other controls using FOR attributes.
Line 123 WCAG2 A 4.1.2
Add a FOR attribute set to the ID of the associated control. Some screen readers ignore labels without FOR attributes.
<label><a><span>All Cuisines</span></a></label></li>
<li class="">
<label> <a><span>Chinese</span></a></label></li>
LABEL elements should be associated with other controls using FOR attributes.
Line 124 WCAG2 A 4.1.2
Add a FOR attribute set to the ID of the associated control. Some screen readers ignore labels without FOR attributes.
<label> <a><span>Chinese</span></a></label></li>
<li class="">
<label> <a><span>Fast Food</span></a></label></li>
LABEL elements should be associated with other controls using FOR attributes.
Line 125 WCAG2 A 4.1.2
Add a FOR attribute set to the ID of the associated control. Some screen readers ignore labels without FOR attributes.
<label> <a><span>Fast Food</span></a></label></li>
<li class="">
<label> <a><span>Halal</span></a></label></li>
LABEL elements should be associated with other controls using FOR attributes.
Line 126 WCAG2 A 4.1.2
Add a FOR attribute set to the ID of the associated control. Some screen readers ignore labels without FOR attributes.
<label> <a><span>Halal</span></a></label></li>
<li class="">
<label> <a><span>Indian</span></a></label></li>
LABEL elements should be associated with other controls using FOR attributes.
Line 127 WCAG2 A 4.1.2
Add a FOR attribute set to the ID of the associated control. Some screen readers ignore labels without FOR attributes.
<label> <a><span>Indian</span></a></label></li>
<li class="">
<label> <a><span>Kebab</span></a></label></li>
LABEL elements should be associated with other controls using FOR attributes.
Line 128 WCAG2 A 4.1.2
Add a FOR attribute set to the ID of the associated control. Some screen readers ignore labels without FOR attributes.
<label> <a><span>Kebab</span></a></label></li>
<li class="">
<label> <a><span>Pizza</span></a></label></li>
LABEL elements should be associated with other controls using FOR attributes.
Line 129 WCAG2 A 4.1.2
Add a FOR attribute set to the ID of the associated control. Some screen readers ignore labels without FOR attributes.
<label> <a><span>Pizza</span></a></label></li>
<li class="">
<label> <a><span>Sushi</span></a></label></li>
LABEL elements should be associated with other controls using FOR attributes.
Line 130 WCAG2 A 4.1.2
Add a FOR attribute set to the ID of the associated control. Some screen readers ignore labels without FOR attributes.
<label> <a><span>Sushi</span></a></label></li>
<li class="">
<label> <a><span>Thai</span></a></label></li>
LABEL elements should be associated with other controls using FOR attributes.
Line 131 WCAG2 A 4.1.2
Add a FOR attribute set to the ID of the associated control. Some screen readers ignore labels without FOR attributes.
<label> <a><span>Thai</span></a></label></li>
</ul>
</div>
</div>
<div class="colRight searchAjaxWrapper" id="rest-results">
<img src="images/misc/menu-preloader-small.gif" alt="Preloader" class="searchAjaxSpinner" id="search-ajax-spinner"
>
End tag for "img" omitted, but OMITTAG NO was specified.
Line 137 HTML Validation
This often occurs in XHTML on tags like IMG, LINK, META and BR when the closing / has been omitted.
This page has malformed tags which IE8 and later treat differently from earlier versions of IE.
Line 137 Internet Explorer ≤ 7.0
Fix the errors listed on the Standards tab of this report.
Markup errors like missing end tags means IE8 and IE9 may display different content from IE6 and IE7.
Google recommends using well-formed HTML code in your webpages. This page has mismatched tags.
Line 137 Google
Fix the critical errors listed on the Standards tab of this report. Markup errors like unclosed comments or unclosed title tags mean search engine may miss important content.
>
<span id="search-ajax-text">loading...</span>
<div class="searchResults">
<div class="breadcrumbBorder" itemtype
="http://schema.org/WebPage" itemscope
="">
There is no attribute "itemtype".
Line 140 HTML Validation
This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen
if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions.
For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes
which were present in earlier versions of HTML.
="http://schema.org/WebPage" itemscope
There is no attribute "itemscope".
Line 140 HTML Validation
This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen
if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions.
For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes
which were present in earlier versions of HTML.
="">
<div class="breadcrumb" itemprop
="breadcrumb">
There is no attribute "itemprop".
Line 142 HTML Validation
This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen
if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions.
For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes
which were present in earlier versions of HTML.
="breadcrumb">
<h1>
<u
l>
Document type does not allow element "ul" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag.
Line 144 HTML Validation
l>
<li class="regular"><a title="Home" href="/">Home</a></li>
<li class="regular current">Takeaways delivering to SW6</li>
</ul>
</h1>
</div>
<div class="searchResults">
<div class="searchItems">
<div class="searchResInfo">
<h2><span>
Showing takeaway restaurants delivering to <b>Fulham and Parson's Green SW6</b>
</span></h2>
</div>
<div class="sortBy sortByCurrentOnline">
<select name="sort[name]" class="restsSortingSelect" style="width:100px;">
This form control has no associated LABEL element.
Add a LABEL tag with the FOR attribute set to the ID of this control. This allows screen readers to tell the user what each control does.
Do not wrap LABEL tags around input controls (implicit labels) since this is very unreliable in older screen readers.
This form has fields without LABEL elements or TITLE attributes.
Line 157 Section 508 1194.22 (n)
Screen readers use LABEL elements or TITLE attributes to describe form fields to non-sighted users.
Without these, forms are very hard to use with a screen reader.
Forms designed to be completed online shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
Use LABEL tags for each data entry field to show what data is expected.
Line 157 Usability.gov 13:5
Make sure each INPUT field has an associated LABEL tag describing the field.
Radio buttons are easier to use than drop-downs when there are 6 choices or less.
Line 157 Usability.gov 13:9
One usability study showed radio buttons give reliably better performance than drop-down lists for mutually exclusive selections.
If screen space allows use radio buttons instead of lists/dropdowns with fewer than 7 items.
<select name="sort[name]" class="restsSortingSelect" style="width:100px;">
<option value="rating" class="restsSortingSelect option">Rating: Highest first</option>
<option value="favorite" class="restsSortingSelect option">Liked: Most Liked first</option>
<option value="online" selected="selected" class="restsSortingSelect option">Recommended</option>
<option value="price" class="restsSortingSelect option">Price: High-End first</option>
<option value="price,rev" class="restsSortingSelect option">Price: Cheapest first</option>
</select>
</div>
</div>
</div>
</div>
<div class="clear"></div>
<div id="search-with-no-js" style="font-weight: bold; color: #000;">No results? If this isn't working, please wait 10 seconds and then
<a href="http://hungryhouse.co.uk/takeaways/fulham-parsons-green-sw6">click here</a> to load the search results again.</div>
Users should be able to quickly look at each link and tell where it goes. Link text:
"click here"
Line 169 Usability.gov 10:1
Don't use generic link labels like "click here" or "read more" because they're hard to tell apart when users scan a page.
<a href="http://hungryhouse.co.uk/takeaways/fulham-parsons-green-sw6">click here</a> to load the search results again.</div>
<scrip
t>$('#search-with-no-js').hide();</script>
Required attribute "type" not specified.
Line 170 HTML Validation
t>$('#search-with-no-js').hide();</script>
</div>
<div id="restsSearchResultsList" style="clear:left; padding-top:10px;">
<div class="restsSearchItemRes">
<div class="restsSearchItemResBox">
</div>
</div>
<div class="restsSearchItemRes">
<div class="restsSearchItemResBox">
</div>
</div>
<div class="restsSearchItemRes">
<div class="restsSearchItemResBox">
</div>
</div>
<div class="restsSearchItemRes">
<div class="restsSearchItemResBox">
</div>
</div>
<div class="restsSearchItemRes">
<div class="restsSearchItemResBox">
</div>
</div>
</div>
</div>
<script type="text/javascript">
$(function () {
$.cookie('hh-js', 1, { expires: 0, path: '/', domain: '.hungryhouse.co.uk' });
$.rests.ajaxLoad(null, null, 'http://hungryhouse.co.uk/takeaways/fulham-parsons-green-sw6');
//setTimeout("$.rests.ajaxLoad(null, null, 'http://hungryhouse.co.uk/takeaways/fulham-parsons-green-sw6');", 200000);
});
</script>
</div>
<br class="clear"/>
<script type="text/javascript">
var options = {
postcode: 'SW6',
postcodeFull: '',
postcodeShort: 'SW6'
};
$.rests.init('http://hungryhouse.co.uk/takeaways/fulham-parsons-green-sw6', 'http://hungryhouse.co.uk/', options);
if ($('.restsSearchByPostCodeBox label.error').length) {
$('.restsSearchByPostCodeBox label.error').tooltip({
position: ['bottom', 'right'],
offset: [14, 0],
opacity: 0.8
});
}
if(typeof orderhistoryInitView == 'function'){
$(function () {
$.ob.orderhistoryInitView();
});
}
$.widget('custom.catcomplete', $.ui.autocomplete, {
_renderMenu: function (ul, items) {
var self = this,
currentCategory = '';
$.each(items, function (index, item) {
if (item.category != currentCategory) {
ul.append("<li class='ui-autocomplete-category
'>" + item.category + "</li>");
Document type does not allow element "li" here.
Line 229 HTML Validation
'>" + item.category + "</li>");
currentCategory = item.category;
}
self._renderItemData(ul, item);
});
}
});
$(function() {
$('#search-suggest').catcomplete({
source: function (request, response) {
$.post($_hh.base + 's.php', {
q: request.term,
rids: $('#rids').val()
},
function (data) {
response($.map(data, function (item) {
return {
label: item.label,
value: item.value,
id: item.id,
category: item.category,
code: item.code,
count: item.count
};
}));
},
'json'
);
},
select: function(event, ui) {
console.log(ui);
if (ui.item.code == 'cuisine') {
var a = document.createElement('a');
a.href = $('.restsFilterBoxCuisines a[rel=' + encodeURIComponent(ui.item.id) + ']').attr('href');
//Getting number of results
numbers = ui.item.count || '';
var link = $_hh.tracking.system.getPostponeTrackingUrl({
type: 'ga',
data: [
'keyword_search_Cuisines',
ui.item.value,
'SW6',
numbers
]
}, a.pathname);
window.location = link;
} else if (ui.item.code == 'rest'){
var link = $_hh.tracking.system.getPostponeTrackingUrl( {
type: 'ga',
data: [
'keyword_search_Restaurant_names',
ui.item.value,
'SW6'
]
}, ($_hh.base + ui.item.id));
window.location = link;
} else if (ui.item.code == 'menu'){
var a = document.createElement('a');
a.href = $('.restsFilterBoxCuisines a[rel=all-cuisine]').attr('href');
$('#search-suggest').val(ui.item.value);
$('.searchButton').trigger('click');
}
},
minLength: 2
});
});
</script>
</div> <!-- end maincontent -->
<div class="clear"></div>
<!-- End body -->
<div id="maincontent-end"></div>
</div> <!-- end main-container -->
<div id="sign-in-popup-wrapper">
<form method="post" action="/?signin=yes" style="margin:0px">
<h4 class="signinHeader">Sign in</h4>
<div class="signinForm">
<p class="signInFormId">
<span class="signinInfo">Sign in with your Member ID and your password...</span>
<label for="sign-in-form-login"><span>Member ID</span></label>
<input id="sign-in-form-login" type="text" name="cust_member_id" value="" tabindex="1"/>
<a href="member_reminder">Forgotten your ID?</a>
</p>
<p class="signInFormPwd">
<label for="sign-in-form-password"><span>Password</span></label>
<input id="sign-in-form-password" type="password" name="cust_password" tabindex="2"/>
<a href="password_reset">Forgotten your Password?</a>
</p>
<!--p class="signInSsl"></p-->
<p>
<input type="hidden" name="home_member_signin_x" value="1" />
<button name="home_member_signin" class="homeMemberSignin" type="submit" tabindex="3"><span>Sign in</span></button>
<a href="https://hungryhouse.co.uk/?signin=yes">
Sign in using secure mode</a>
</p>
</div>
<div class="signinSocial">
<span class="signinInfo">Sign in with your Facebook account</span><div class=" "><a href="/openid/redirect/facebook/" class="facebookSignIn"><span>Facebook</span></a></div></div></form>
<div class="signinJoin">Not a member? <a href="join" title="Join to Hungryhouse">Join now</a></div>
</div><script type="text/javascript">
$(document).ready(function() {
$("#guest-login-button").attr("href", $("#guest-login-button").attr("rel")).fancybox({
autoScale : false,
fitToView : false,
height : 575,
width : 440,
fitToView : false,
autoSize : false,
closeClick : false,
wrapCSS : "fancybox-signin",
closeBtn : true,
openEffect : "fade",
closeEffect : "fade",
padding : 0
});
});
</script>
<div id="membership-benefits-wrapper"><div id="membership-benefits" class="tooltip"><h3>Why become a member?</h3><ul>
<li>Save your details for faster, easier ordering</li>
<li>One-click re-ordering of previous meals from your order history</li>
<li>'Like' restaurants, to make it easier to find them next time you visit hungryhouse</li>
<li>Leave personalized notes about any restaurant - eg "their pork balls are amazing!!"</li>
<li>Opt-in for email updates of special offers and new menus in your area</li>
</ul>
<p>Own a restaurant? <a href="restaurateurs2">Contact us</a></p></div></div>
<script type="text/javascript">
$(document).ready(function() {
if($("#guest-join-button").length){
var tmp = $("#membership-benefits").clone();
$("#membership-benefits-wrapper").remove();
$("#guest-join-button").after(tmp);
$("#guest-join-button").tooltip({
position: ["bottom", "right"],
offset: [14, 0],
opacity: 0.8
});
}
});
</script>
</div>
<div id="footer" class="footer">
<div class="section footerLinks">
<div class="footerBox">
<h3>Get our mobile app</h3>
<a href="https://play.google.com/store/apps/details?id=com.hungryhouse" class="appAndroid"><i class="iconAndroid"></i><span>Android App</span></a>
Provide a way to skip repetitive navigation links.
Line 395 Section 508 1194.22 (o)
Without a skip link, screen readers read out the navigation links on every page before reading the page content.
Headings can be a substitute in limited circumstances, but they're not used by all screen reader users,
and many other assistive technology users have no way to navigate via headings.
Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users:
<a class="accessible" href="#main">[Skip to Content]</a>
<a href="http://itunes.apple.com/gb/app/hungryhouse-order-takeaway/id400227047?mt=8" class="appApple"><i class="iconApple"></i><span>iPhone App</span></a>
<a href="http://hungryhouse.co.uk/blog/dragons-den/" class="appBBC"><i class="iconBBC"></i><span>BBC</span></a>
</div>
<div class="footerBox">
<h3>Company</h3>
<ul>
<li><a href="about"><span>About Us</span></a></li>
<li>
<a href="recommendations" rel="nofollow"><span>Recommend Restaurant</span></a></li>
Using rel="nofollow" on internal links dilutes PageRank flow through your site.
Line 402 Google
PageRank is distributed amongst all outgoing links on a page (including the nofollow links),
so PageRank flowing to internal nofollow links vanishes.
<a href="recommendations" rel="nofollow"><span>Recommend Restaurant</span></a></li>
<li>
<a href="restaurateurs" rel="nofollow"><span>Restaurateurs</span></a></li>
Using rel="nofollow" on internal links dilutes PageRank flow through your site.
Line 403 Google
PageRank is distributed amongst all outgoing links on a page (including the nofollow links),
so PageRank flowing to internal nofollow links vanishes.
<a href="restaurateurs" rel="nofollow"><span>Restaurateurs</span></a></li>
<li>
<a href="partner" rel="nofollow"><span>Partner Portal</span></a></li>
Using rel="nofollow" on internal links dilutes PageRank flow through your site.
Line 404 Google
PageRank is distributed amongst all outgoing links on a page (including the nofollow links),
so PageRank flowing to internal nofollow links vanishes.
<a href="partner" rel="nofollow"><span>Partner Portal</span></a></li>
<li>
<a href="contact" rel="nofollow"><span>Contact Us</span></a></li>
Using rel="nofollow" on internal links dilutes PageRank flow through your site.
Line 405 Google
PageRank is distributed amongst all outgoing links on a page (including the nofollow links),
so PageRank flowing to internal nofollow links vanishes.
<a href="contact" rel="nofollow"><span>Contact Us</span></a></li>
<li><a href="blog/"><span>Blog</span></a></li>
<li><a href="sitemap"><span>Sitemap</span></a></li>
<li>
<a href="faq" title="FAQ" rel="nofollow"><span>Frequently Asked Questions</span></a></li>
Using rel="nofollow" on internal links dilutes PageRank flow through your site.
Line 408 Google
PageRank is distributed amongst all outgoing links on a page (including the nofollow links),
so PageRank flowing to internal nofollow links vanishes.
<a href="faq" title="FAQ" rel="nofollow"><span>Frequently Asked Questions</span></a></li>
<li><a href="faq/Gift%20Vouchers" title="Gift Vouchers"><span>Gift Vouchers</span></a></li>
</ul>
</div>
<div class="footerBox">
<h3>Now serving</h3>
<ul>
<li><a href="birmingham_takeaway"><span>Birmingham</span></a></li>
<li><a href="brighton_takeaway"><span>Brighton</span></a></li>
<li><a href="glasgow_takeaway"><span>Glasgow</span></a></li>
<li><a href="leeds_takeaway"><span>Leeds</span></a></li>
<li><a href="leicester_takeaway"><span>Leicester</span></a></li>
<li><a href="liverpool_takeaway"><span>Liverpool</span></a></li>
<li><a href="london_takeaway"><span>London</span></a></li>
<li><a href="manchester_takeaway"><span>Manchester</span></a></li>
<li><a href="newcastle_takeaway"><span>Newcastle</span></a></li>
<li><a href="sheffield_takeaway"><span>Sheffield</span></a></li>
<li><a href="takeaway"><span>All locations</span></a></li>
</ul>
</div>
<div class="footerBox">
<h3>Best Takeaways</h3>
<ul>
<li><a href="indian_takeaway"><span>Indian Takeaway</span></a></li>
<li><a href="chinese_takeaway"><span>Chinese Takeaway</span></a></li>
<li><a href="thai_takeaway"><span>Thai Takeaway</span></a></li>
<li><a href="pizza"><span>Pizza Delivery</span></a></li>
<li><a href="sushi"><span>Sushi Delivery</span></a></li>
<li><a href="halal_takeaway"><span>Halal Takeaway</span></a></li>
<li><a href="takeaway"><span>All takeaway cuisines</span></a></li>
</ul>
</div>
</div>
<div class="section copyRights">
<div id="logos">
Using rel="nofollow" on internal links dilutes PageRank flow through your site.
Line 447 Google
PageRank is distributed amongst all outgoing links on a page (including the nofollow links),
so PageRank flowing to internal nofollow links vanishes.
<a class="footLinkNectar" href="news/Awards/hungryhouse-takes-top-business-award_875" title="hungryhouse takes top business award" rel="nofollow"><span>hungryhouse takes top business award</span></a>
Provide a way to skip repetitive navigation links.
Line 448 Section 508 1194.22 (o)
Without a skip link, screen readers read out the navigation links on every page before reading the page content.
Headings can be a substitute in limited circumstances, but they're not used by all screen reader users,
and many other assistive technology users have no way to navigate via headings.
Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users:
<a class="accessible" href="#main">[Skip to Content]</a>
Using rel="nofollow" on internal links dilutes PageRank flow through your site.
Line 448 Google
PageRank is distributed amongst all outgoing links on a page (including the nofollow links),
so PageRank flowing to internal nofollow links vanishes.
<a class="footLinkSmartest" title="Hungryhouse recognised as one of the UK's smartest small businesses" href="news/Press%20releases/hungryhouse-recognised-as-one-of-the-uk-s-smartest-small-businesses_701" rel="nofollow"><span>Hungryhouse recognised as one of the UK’s smartest small businesses</span></a>
Using rel="nofollow" on internal links dilutes PageRank flow through your site.
Line 449 Google
PageRank is distributed amongst all outgoing links on a page (including the nofollow links),
so PageRank flowing to internal nofollow links vanishes.
<a class="footLinkReward" title="Hungryhouse rewarded for its innovation" href="news/What%20We%20Are%20Excited%20About/hungryhouse-rewarded-for-its-innovation_688" rel="nofollow"><span>Hungryhouse rewarded for its innovation</span></a>
Using rel="nofollow" on internal links dilutes PageRank flow through your site.
Line 450 Google
PageRank is distributed amongst all outgoing links on a page (including the nofollow links),
so PageRank flowing to internal nofollow links vanishes.
<a class="footLinkDragon" href="news/Videos/hungryhouse-co-uk-tempts-dragons-to-a-takeaway_156" title="Dragons Den" rel="nofollow"><span>Dragons Den</span></a>
</div>
©2007-2014 hungryhouse.com limited | 78 York Street, London, W1H 1DP. <br />
Using rel="nofollow" on internal links dilutes PageRank flow through your site.
Line 454 Google
PageRank is distributed amongst all outgoing links on a page (including the nofollow links),
so PageRank flowing to internal nofollow links vanishes.
<a href="privacy" title="Privacy Policy" rel="nofollow">Privacy Policy</a><span>|</span>
Provide a way to skip repetitive navigation links.
Line 455 Section 508 1194.22 (o)
Without a skip link, screen readers read out the navigation links on every page before reading the page content.
Headings can be a substitute in limited circumstances, but they're not used by all screen reader users,
and many other assistive technology users have no way to navigate via headings.
Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users:
<a class="accessible" href="#main">[Skip to Content]</a>
Using rel="nofollow" on internal links dilutes PageRank flow through your site.
Line 455 Google
PageRank is distributed amongst all outgoing links on a page (including the nofollow links),
so PageRank flowing to internal nofollow links vanishes.
<a href="terms" title="Terms of Use" rel="nofollow">Terms of Use</a><span>|</span>
Using rel="nofollow" on internal links dilutes PageRank flow through your site.
Line 456 Google
PageRank is distributed amongst all outgoing links on a page (including the nofollow links),
so PageRank flowing to internal nofollow links vanishes.
<a href="cookies" title="About cookies" rel="nofollow">About Cookies</a><span>|</span>
<a href="/~m/">Mobile site</a>
<br />
<div class="aDeliveryHeroCompany">
<a href="http://www.deliveryhero.com/" rel="external,nofollow" title="A Delivery Hero Company" target="_blank">
<img src="http://static.hungryhouse.co.uk/images/ads/dh_black.png?30" alt="A Delivery Hero Company" />
</a>
</div>
<div class="disclaimer"> </div>
</div>
</div><!-- BEGIN:tracking codes body bottom -->
<script type="text/javascript" src="http://static.hungryhouse.co.uk/include/tracking.system.js?30"></script><script type="text/javascript">
(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();
</script><script type="text/javascript">var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-650065-1']);
_gaq.push(['_setDomainName', '.hungryhouse.co.uk']);
_gaq.push(['_addIgnoredRef', 'hungryhouse.co.uk']);
_gaq.push(['_setAllowAnchor', true]);
_gaq.push(['_setCampaignCookieTimeout', '2592000000']);_gaq.push('_setVar', 'rebrand');_gaq.push('_setCustomVar', 1, 'design', 'rebrand');_gaq.push(['_trackPageview', location.pathname + '+searchresults/' + location.search]);
_gaq.push(["_trackEvent", "Postcode", "SW6", "search"]);
_gaq.push(["_trackEvent", "Restaurant_list_sort", "Recommended", "sw6", 0]);
_gaq.push(["_trackEvent", "Search guest", "Partial postcode"]);
$_hh.tracking.base.register("ga", ['event', 'trans', 'ga', 'gajax', 'error'], function (type, category, action, opt_label, opt_value) {
opt_value = parseInt(opt_value);
if (isNaN(opt_value)) {
opt_value = null;
}
if (type != "trans") {
_gaq.push(["_trackEvent", category, action, opt_label, opt_value]);
}
});
</script>
<script type="text/javascript">var google_tag_params = {"pageType":"other_pages","partpostcode":"","fullpostcode":"","city":"","restaurantname":"","restaurantID":"","cuisine":"","post_partpostcode":"","post_fullpostcode":"","post_city":"","post_restaurantname":"","post_restaurantID":"","post_cuisine":"","post_basketValue":"","post_date":"","post_dayOfWeek":"","post_gender":"","post_numberofOrder":""};</script>
<script type="text/javascript">
/* <![CDATA[ */
var google_conversion_id = 996602259;
var google_conversion_label = "ZaqACN2U1QQQk-Ob2wM";
var google_custom_params = window.google_tag_params;
var google_remarketing_only = true;
/* ]]> */
</script>
<script type="text/javascript" src="//www.googleadservices.com/pagead/conversion.js">
</script>
<noscript>
<div style="display:inline;">
<img height="1" width="1" style="border-style:none;" alt="" src="//googleads.g.doubleclick.net/pagead/viewthroughconversion/996602259/?value=0&label=ZaqACN2U1QQQk-Ob2wM&guid=ON&script=0"/>
</div>
</noscript>
<script type="text/javascript">$(window).load(function() {
$('body').append('<s
c'+'rip'+'t async="" src="http://www.dwin1.com/3898.js"></
s'+'cri'+'pt>');
An attribute specification must start with a name or name token.
Line 512 HTML Validation
Element "sc" undefined.
Line 512 HTML Validation
This happens when the version of HTML used on this page doesn't support an element with this name. This can happen
if the element is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions.
For example, HTML 4 DOCTYPEs don't allow HTML 5 element and Strict DOCTYPEs don't allow stylistic elements
and frames which were present in earlier versions of HTML.
This page has malformed tags which IE8 and later treat differently from earlier versions of IE.
Line 512 Internet Explorer ≤ 7.0
Fix the errors listed on the Standards tab of this report.
Markup errors like missing end tags means IE8 and IE9 may display different content from IE6 and IE7.
Google recommends using well-formed HTML code in your webpages. This page has mismatched tags.
Line 512 Google
Fix the critical errors listed on the Standards tab of this report. Markup errors like unclosed comments or unclosed title tags mean search engine may miss important content.
c'+'rip'+'t async="" src="http://www.dwin1.com/3898.js"></
Delimiter "'" invalid: only S separators and TAGC allowed here.
Line 512 HTML Validation
End tag for element "s" which is not open.
Line 512 HTML Validation
This page has malformed tags which IE8 and later treat differently from earlier versions of IE.
Line 512 Internet Explorer ≤ 7.0
Fix the errors listed on the Standards tab of this report.
Markup errors like missing end tags means IE8 and IE9 may display different content from IE6 and IE7.
Google recommends using well-formed HTML code in your webpages. This page has mismatched tags.
Line 512 Google
Fix the critical errors listed on the Standards tab of this report. Markup errors like unclosed comments or unclosed title tags mean search engine may miss important content.
s'+'cri'+'pt>');
});
</scrip
t><script type="text/javascript">
End tag for "sc" omitted, but OMITTAG NO was specified.
Line 514 HTML Validation
This often occurs in XHTML on tags like IMG, LINK, META and BR when the closing / has been omitted.
This page has malformed tags which IE8 and later treat differently from earlier versions of IE.
Line 514 Internet Explorer ≤ 7.0
Fix the errors listed on the Standards tab of this report.
Markup errors like missing end tags means IE8 and IE9 may display different content from IE6 and IE7.
Google recommends using well-formed HTML code in your webpages. This page has mismatched tags.
Line 514 Google
Fix the critical errors listed on the Standards tab of this report. Markup errors like unclosed comments or unclosed title tags mean search engine may miss important content.
t><script type="text/javascript">
$(window).load(function() {
(function() {
var d=document,
h=d.getElementsByTagName('head')[0],
s=d.createElement('script');
s.type='text/javascript';
s.async=true;
s.src='http://static.hungryhouse.co.uk/include/tracking.maxemail.js?30';
h.appendChild(s);
}());
}); </script><script type="text/javascript"><!--
document.write(unescape("%3Cscript id='pap_x2s6df8d' src='http://pap.hungryhouse.co.uk/scripts/trackjs.js' type='text/javascript'%3E%3C/script%3E"));//-->
</script>
<script type="text/javascript"><!--
try {
PostAffTracker.setAccountId('default1');
PostAffTracker.disableTrackingMethod('F');
PostAffTracker.track();
} catch (err) { }
//-->
</script><script type="text/javascript">
$(window).load(function() {
var d=document,
h=d.getElementsByTagName('body')[0],
s=d.createElement('img');
s.src='/os.gif?os=http://hungryhouse.co.uk/search_loading&(none)';
s.width=1; s.height=1;
s.className='os';
s.alt='';
h.appendChild(s);
});
</script>
<noscript><img alt="" width="1" height="1" class="os" src="/os.gif?os=http://hungryhouse.co.uk/search_loading&(none)" /></noscript><script type="text/javascript">
var GoSquared = {};
GoSquared.acct = 'GSN-178163-Q';
(function (w) {
function gs() {
w._gstc_lt = +new Date;
var d = document, g = d.createElement('script');
g.type = 'text/javascript';
g.src = '//d1l6p2sc9645hc.cloudfront.net/tracker.js';
var s = d.getElementsByTagName('script')[0];
s.parentNode.insertBefore(g, s);
}
w.addEventListener ? w.addEventListener('load', gs, false) : w.attachEvent('onload', gs);
})(window);
</script>
<script type="text/javascript" src="//static.criteo.net/js/ld/ld.js" async
="true"></script>
There is no attribute "async".
Line 562 HTML Validation
This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen
if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions.
For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes
which were present in earlier versions of HTML.
="true"></script>
<script type="text/javascript">
$_hh.tracking.base.register("crt", ['criteo'], function(type, category, action, opt_label, opt_value){
if (typeof (action) !== "string") {
action = "" + action;
}
action = action.split(",");
window.criteo_q = window.criteo_q || [];
window.criteo_q.push(
{ event: "setAccount", account:11901},
{ event: "setCustomerId", id: "" },
{ event: "setSiteType", type: "d" },
{event: "viewList", item:action}
);
});
</script><!-- END:tracking codes body bottom -->
<scrip
t>$(document).ready(function(){$('input[type="checkbox"], input[type="radio"]').uniform();})</script><scrip
t>
Required attribute "type" not specified.
Line 579 HTML Validation
t>$(document).ready(function(){$('input[type="checkbox"], input[type="radio"]').uniform();})</script><scrip
Required attribute "type" not specified.
Line 579 HTML Validation
t>
if($_hh.deviceInfo.type.ipad){
$(".tooltip , .tooltipPopup, .toolTipPopup").each(function(){
$(this).unbind();
});
}
</script><script type="text/javascript">$(document).ready(function(){
if($_hh){
if($_hh.deviceInfo){
if($_hh.deviceInfo.type){
for(var i in $_hh.deviceInfo.type){
if($_hh.deviceInfo.type[i]){
$("body").addClass("deviceMobile");
break;
}
}
}
}
}
});</script>
</body>
</html>