Website review, no card needed
detroitwingco.com website review
Visit site (opens in a new tab)Reviewed 20 October 202636 issues · 88 checks
This review found 36 issues worth fixing on detroitwingco.com, 9 of them high impact, across 88 checks. The most urgent: improve image delivery. 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
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.5 s |
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 121 ms |
| May 9, 2026 | 122 ms |
| May 16, 2026 | 123 ms |
| May 23, 2026 | 125 ms |
| May 30, 2026 | 126 ms |
| Jun 6, 2026 | 126 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 130 ms |
| Jun 27, 2026 | 135 ms |
| Jul 4, 2026 | 137 ms |
| Jul 11, 2026 | 135 ms |
| Jul 18, 2026 | 129 ms |
| Jul 25, 2026 | 128 ms |
| Aug 1, 2026 | 126 ms |
| Aug 8, 2026 | 128 ms |
| Aug 15, 2026 | 131 ms |
| Aug 22, 2026 | 133 ms |
| Aug 29, 2026 | 135 ms |
| Sep 5, 2026 | 133 ms |
| Sep 12, 2026 | 134 ms |
| Sep 19, 2026 | 135 ms |
| Sep 26, 2026 | 134 ms |
| Oct 3, 2026 | 135 ms |
| Oct 10, 2026 | 134 ms |
| Oct 17, 2026 | 134 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
12.2 s · 2.4 MB5 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 12.2 s faster on a phone.
Reduce unused JavaScript
2.3 s · 775 KiBAbout 775 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Render-blocking requests
2.1 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
8 third-party services on the page
8 third-party services load with your homepage (audioeye.com, Google Tag Manager and Facebook and others), adding 1.7 MB and 1.6 s of main-thread time.
Mobile performance score: 56
56/100Your mobile performance score is 56 (desktop: 49). Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
500 ms · 371 KiB13 files are served with short cache lifetimes, so returning visitors download them again (371 KiB).
audioeye.com adds 702 ms
702 msaudioeye.com costs a phone 702 ms of main-thread work and 297 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.
Google Tag Manager adds 605 ms
605 msGoogle Tag Manager costs a phone 605 ms of main-thread work and 908 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.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 201 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 27 KiBAbout 27 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
150 ms · 18 KiB18 KiB could be saved by minifying JavaScript.
Legacy JavaScript
38 KiBPolyfills for old browsers add 38 KiB JavaScript that modern phones do not need.
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.
Duplicated JavaScript
2 KiB2 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 20.5 s
20.5 sYour largest element takes 20.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 20.5 s
20.5 sThe page becomes fully interactive after 20.5 s. Good is under 3.8 s.
Total Blocking Time: 508 ms
508 msScripts block taps and scrolling for 508 ms in total while the page loads. Good is under 200 ms.
Speed Index: 4.8 s
4.8 sVisually, the page fills in at 4.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 121 ms to 134 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 113 ms
113 msReal visitors wait 113 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 377 ms
377 msReal visitors wait 377 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.6 MB in 83 requests
4.6 MBYour homepage downloads 4.6 MB in 83 requests on a phone: images 2.5 MB (13), scripts 1.9 MB (31) and fonts 120 KiB (3). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 2.0 MB together. On a phone connection a single image that size takes seconds.
5 images in older formats
5 images (2.5 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.
About 1.3 g of CO₂ per visit
1.29 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.29 g of CO₂e: 155.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 5 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
33 internal links, 42 external
The homepage links to 33 pages on detroitwingco.com and 42 external pages.
7 checks passed
Meta description: 137 characters
Your meta description is 137 characters: “Detroit Wing Co. - Voted Best Wings | Chef Driven Sauces | Fresh Wraps | Chicken Sandwiches | Homemade Sides | Boneless…”.
One H1 headline
Your main headline reads: “ORDER NOW”.
Title: 58 characters
Your title is a healthy 58 characters: “Detroit Wing Co. | Bigger Wings, Wraps, Chicken Sandwiches”.
Canonical URL set
The canonical URL is https://detroitwingco.com/.
Structured data in place
Structured data found: BreadcrumbList, FoodEstablishment, Organization, WebPage and WebSite.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://detroitwingco.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://detroitwingco.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.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (308 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://detroitwingco.com/locations and https://detroitwingco.com/detroitwingco.com/locations all use the title “Locations - Detroit Wing Company”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://detroitwingco.com/rewards, https://detroitwingco.com/catering and https://detroitwingco.com/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://detroitwingco.com/locations and https://detroitwingco.com/detroitwingco.com/locations use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://detroitwingco.com/detroitwingco.com/locations, whose canonical is https://detroitwingco.com/locations. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
7 pages without an H1
https://detroitwingco.com/about, https://detroitwingco.com/dwc-news-and-press, https://detroitwingco.com/careers, https://detroitwingco.com/contact, https://detroitwingco.com/sauces and https://detroitwingco.com/locations and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://detroitwingco.com/contact has 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.
2 pages slow to respond
https://detroitwingco.com/dwc-news-and-press and https://detroitwingco.com/careers took over 3 s to send their HTML from our server.
11 internal pages checked
We fetched 11 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 11 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://wsv3cdn.audioeye.com/static-scripts/v2/2026-10-19b/compliance.css' from origin 'ht…”.
2 checks passed
Tap targets are thumb-sized
34 of 36 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 246 words
The homepage has only about 246 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT” and “ORDER NOW”.
7 calls to action
The homepage has 7 calls to action, for example “Contact”, “Order Now” and “ORDER NOW”.
1 short form
A short form (2 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
12 cookies set on arrival
12Opening the homepage sets 12 cookies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
25 other companies contacted
Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 detroitwingco.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on detroitwingco.com, including 15 speed issues, 1 SEO issue and 4 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.