34-restaurant.co.uk

We performed a comprehensive analysis of 34-restaurant.co.uk on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 922ms. The page is served over HTTP/1.1 protocol, however no compression (Gzip or Brotli) is enabled, which means the page is transferred at its full uncompressed size. The total page weight is 62 KB. Warning: The website does not have a valid SSL certificate. Visitors may see security warnings in their browser, and data transmitted to and from this website is not encrypted. The security headers analysis reveals a score of 0/100 (poor). No security headers are configured, which is a significant security concern. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy, which could expose the site and its users to cross-site scripting (XSS), clickjacking, and other web-based attacks. Our technology detection scan identified 8 technologies across 8 categories powering 34-restaurant.co.uk. The detected stack includes WordPress 7.0, Bootstrap, Google Analytics 4, Google Tag Manager, reCAPTCHA v3, Cloudflare, jQuery, and NitroPack. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, 34-restaurant.co.uk receives an overall trust score of 63/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, 34-restaurant.co.uk receives a trust score of 63/100, which places it in the "Likely Safe" category. This score is calculated by evaluating multiple factors including SSL certificate validity, domain registration history, email authentication protocols, security header configuration, and blacklist status across major threat intelligence databases. The analysis identified several positive trust signals: a valid HTTPS connection protecting data in transit, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a quarantine policy, DKIM (DomainKeys Identified Mail) providing cryptographic email verification, and DNSSEC providing authenticated DNS responses. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking), missing Referrer-Policy, potentially leaking URL information to third parties, and the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked 34-restaurant.co.uk against 8 major blacklist databases including Google Safe Browsing, Phishtank, Urlhaus, Openphish, Dnsfilter, Spamhaus Dbl, Surbl, and Virustotal. The domain passed all 8 checks with a clean status, meaning it has not been flagged for phishing, malware distribution, spam, or other malicious activities by any of the tested threat intelligence providers.

Our technology detection engine scanned 34-restaurant.co.uk and identified 8 distinct technologies across 8 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. CMS: WordPress (version 7.0) — manages the content and page structure for 34-restaurant.co.uk. CSS Framework: Bootstrap — provides the styling and responsive layout system for 34-restaurant.co.uk. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for 34-restaurant.co.uk. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for 34-restaurant.co.uk. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for 34-restaurant.co.uk. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for 34-restaurant.co.uk. JavaScript Library: jQuery — provides utility functions and DOM manipulation for 34-restaurant.co.uk. Performance: NitroPack — optimizes page loading speed and performance for 34-restaurant.co.uk. We also extracted the following tracking identifiers: Google Tag Manager container GTM-N98CKDH. These IDs can be used to identify other websites operated by the same organization.

34-restaurant.co.uk delivers its homepage in 922ms (server response time), which is considered average by industry standards. The total page weight is 62 KB, and we detected 87 resource requests loading assets from 9 third-party domains. A high number of third-party domains can significantly impact page load time due to additional DNS lookups and TLS handshakes required for each domain. No compression is currently enabled on 34-restaurant.co.uk. Enabling Brotli or Gzip compression could reduce page size by 60-80% for text-based assets (HTML, CSS, JavaScript), significantly improving load times and reducing bandwidth costs. This is one of the simplest and most impactful performance optimizations available. Asset minification status: 2 out of 8 CSS files and 8 out of 14 JavaScript files are minified. Minifying the remaining 12 unminified file(s) could further reduce page weight by 10-30% for those assets. Minification is a best practice that reduces download sizes without affecting functionality. From an environmental perspective, each page view of 34-restaurant.co.uk produces approximately 0.03g of CO₂, earning a carbon rating of A. This places the website among the cleanest on the web, demonstrating efficient use of server resources and optimized content delivery. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 62 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for 34-restaurant.co.uk. This typically means the site doesn't have enough real-world Chrome user traffic to generate statistically significant field data, or the domain is not included in the CrUX dataset. Core Web Vitals (LCP, INP, CLS) are important Google ranking factors that measure real user experience.

34-restaurant.co.uk resolves to the IPv4 address 212.71.245.228, but does not support IPv6. IPv6 adoption is increasingly important as IPv4 address space becomes exhausted, and some ISPs and regions are transitioning to IPv6-only connectivity. The domain has 1 A record(s) configured. The domain name system is managed by 2 name servers: hugh.ns.cloudflare.com and phoenix.ns.cloudflare.com. Having 2 name servers provides good redundancy — if one fails, the others can continue serving DNS queries. The choice of name servers often indicates the DNS hosting provider or CDN service being used. Email for 34-restaurant.co.uk is handled by Microsoft 365 with 1 MX records configured: 34restaurant-co-uk0e.mail.protection.outlook.com. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. SPF (Sender Policy Framework) is configured, which specifies which mail servers are authorized to send email on behalf of this domain. This helps prevent email spoofing and improves email deliverability. DMARC (Domain-based Message Authentication, Reporting and Conformance) is configured with a quarantine policy — a moderate setting, directing unauthorized emails to spam/junk folders. DKIM (DomainKeys Identified Mail) is configured, adding a cryptographic signature to outgoing emails that receiving servers can verify to confirm the email hasn't been tampered with in transit. DNSSEC is enabled for 34-restaurant.co.uk, providing an additional layer of security by cryptographically signing DNS records. This prevents DNS cache poisoning and man-in-the-middle attacks that could redirect visitors to malicious websites. Our subdomain enumeration scan discovered 2 active subdomains for 34-restaurant.co.uk: m.34-restaurant.co.uk and www.34-restaurant.co.uk. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of 34-restaurant.co.uk contains 469 words of visible text content. This is a moderate amount of content. The page is structured with 3 H2 headings, 4 H3 headings, 0 H4 headings. The page includes 16 images. 14 images (88%) are missing alt text attributes, which is a significant concern for both accessibility and SEO. Screen readers rely on alt text to describe images to visually impaired users, and search engines use alt text to understand image content. Only 12% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 25 internal links pointing to other pages on the same domain and 8 external links pointing to third-party websites. There are 14 external JavaScript files, 8 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages), Schema.org structured data (BarOrPub, GeoCoordinates, OpeningHoursSpecification, PostalAddress, and Restaurant), and RSS feed for content syndication. Notable missing features: robots.txt. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on 34-restaurant.co.uk: Discover. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates.

The title tag for 34-restaurant.co.uk is good at 65 characters: "Mayfair Restaurants | Steak & Fish Restaurant London | 34 Mayfair". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 242 characters (slightly long): "34 Mayfair is a modern grill restaurant in Mayfair, central London, with a focus on meat, fish and seasonal ingredients,...". Google typically displays up to 155-160 characters of the meta description in search results. A compelling meta description with a clear call-to-action can significantly improve click-through rates from search results. The canonical url is correctly set to https://34-restaurant.co.uk/, preventing duplicate content issues, the meta robots directive is set to max-image-preview:large, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to 34-restaurant.co.uk on social media, the platform will have to guess the title, description, and image — often producing unattractive or inaccurate previews. Adding OG tags is essential for social media marketing. The site implements Schema.org structured data with the following types: BarOrPub, GeoCoordinates, OpeningHoursSpecification, PostalAddress, and Restaurant. Structured data helps search engines understand the page content and can enable rich results (featured snippets, knowledge panels, star ratings) in Google search results, which can significantly increase click-through rates.