Website review, no card needed
danahospitality.net website review
Visit site (opens in a new tab)Reviewed 1 November 202635 issues · 73 checks
This review found 35 issues worth fixing on danahospitality.net, 14 of them high impact, across 73 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
68DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.9 s
1.3 s
1.8 s
2.2 s
2.6 s
3.1 s
3.5 s
Speed
Reduce unused JavaScript
2.5 s · 566 KiBAbout 566 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.
Render-blocking requests
1.1 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Improve image delivery
500 ms · 2.1 MB9 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Use efficient cache lifetimes
950 ms · 172 KiB7 files are served with short cache lifetimes, so returning visitors download them again (172 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Hotjar and Cloudflare CDN and others), adding 1.1 MB and 942 ms of main-thread time.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 525 ms
525 msGoogle Tag Manager costs a phone 525 ms of main-thread work and 638 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Legacy JavaScript
150 ms · 26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 139 ms. During a long task the page ignores taps.
Reduce unused CSS
23 KiBAbout 23 KiB of CSS is downloaded but never applied on this page.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 993 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 19.3 s
19.3 sYour largest element takes 19.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Signature Dining Great food. Empowered people. The perfect …”.
Time to Interactive: 19.9 s
19.9 sThe page becomes fully interactive after 19.9 s. Good is under 3.8 s.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 389 ms
389 msScripts block taps and scrolling for 389 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Cumulative Layout Shift: 0.02
0.02The layout barely moves while loading (CLS 0.02, good is under 0.1).
Images and page weight
Page weight: 9.0 MB in 93 requests
9.0 MBYour homepage downloads 9.0 MB in 93 requests on a phone: media 4.8 MB (2), images 2.9 MB (18) and scripts 1.2 MB (44). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
[email protected] weighs 777 KiB. On a phone connection a single image that size takes seconds.
4 images far larger than shown
828 KiB4 images are downloaded at several times the size a phone draws them, for example [email protected] at 598 px wide, shown at 110 px. Resized copies would save about 828 KiB.
9 images in older formats
9 images (2.2 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
9 images below the first screen load straight away
9 images further down the page (2.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.6 g of CO₂ per visit
2.56 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.56 g of CO₂e: 306.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (31 elements)
All page content should be contained by landmarks: 31 elements on the page fail this check, rated moderate by axe-core.
1 checks passed
32 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 34 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
robots.txt blocks all crawlers
Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.
Blocked from indexing
Google's crawler is blocked from indexing this page.
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “Canada’s Food Service Provider of Choice | Dexterra Signature Dining”.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
56 internal links, 7 external
The homepage links to 56 pages on danahospitality.net and 7 external pages.
6 checks passed
Meta description: 114 characters
Your meta description is 114 characters: “Our recipe is simple: freshness, culinary freedom & seasonally inspired menus. Get a taste of the Dana difference.”.
One H1 headline
Your main headline reads: “Signature Dining”.
Canonical URL set
The canonical URL is https://dana1.wpengine.com/en-ca/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
XML sitemap found
Your XML sitemap is reachable at https://dana1.wpengine.com/sitemap.xml.
AI search readiness
robots.txt blocks 6 AI answer engine crawlers
6 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://dana1.wpengine.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
Other pages
3 pages without a meta description
https://dana1.wpengine.com/en-ca/our-services, https://dana1.wpengine.com/en-ca/who-we-serve and https://dana1.wpengine.com/en-ca/about-dana have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://dana1.wpengine.com/contact, whose canonical is https://dana1.wpengine.com/en-ca/contact. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://dana1.wpengine.com/en-ca/our-services, https://dana1.wpengine.com/en-ca/who-we-serve and https://dana1.wpengine.com/en-ca/about-dana have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://dana1.wpengine.com/en-ca/our-services, https://dana1.wpengine.com/en-ca/who-we-serve and https://dana1.wpengine.com/en-ca/about-dana have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 small tap targets
2 of 6 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Looks like your website URL has changed. To ensure the proper functioning of your banner, update the re…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 130 words
The homepage has only about 130 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us”.
9 calls to action
The homepage has 9 calls to action, for example “Contact Us”, “Learn more” and “Download the brochure”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Hotjar (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
20 other companies contacted
Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at danahospitality.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on danahospitality.net, including 13 speed issues, 4 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.