Website review, no card needed
inthooz.com website review
Visit site (opens in a new tab)Reviewed 21 November 202633 issues · 81 checks
This review found 33 issues worth fixing on inthooz.com, 13 of them high impact, across 81 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
77C- #68,586 of 123,419 reviewed websitesbeats 39%
- #44,447 of 69,543 online storesbeats 31%
- #1,094 of 2,883 WooCommerce storesbeats 57%
Closest competitors among WooCommerce stores
Compare side by sideOne score from every part of this review. How it works
Speed
Improve image delivery
72.5 s · 36.9 MB14 images could be 36.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 72.5 s faster on a phone.
Render-blocking requests
2.5 s32 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Use efficient cache lifetimes
10.1 MB16 files are served with short cache lifetimes, so returning visitors download them again (10.1 MB).
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
Font display
700 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 700 ms).
Reduce unused CSS
600 ms · 100 KiBAbout 100 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Reduce unused JavaScript
600 ms · 100 KiBAbout 100 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Hubspot and FontAwesome CDN and others), adding 437 KiB and 177 ms of main-thread time.
Minify JavaScript
150 ms · 6 KiB6 KiB could be saved by minifying JavaScript.
Minify CSS
150 ms · 4 KiB4 KiB could be saved by minifying CSS.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 90 ms. During a long task the page ignores taps.
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 466 ms of it running JavaScript. That is comfortably low.
Server response: 31 ms
31 msYour server sent the HTML in 31 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 112.7 s
112.7 sYour largest element takes 112.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FEATURED CLIENT: Encore Education is changing the rules of …”.
Time to Interactive: 115.8 s
115.8 sThe page becomes fully interactive after 115.8 s. Good is under 3.8 s.
Speed Index: 7.6 s
7.6 sVisually, the page fills in at 7.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
34 images without width and height
34 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.
2 checks passed
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Total Blocking Time: 64 ms
64 msScripts block the page for only 64 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 73.0 MB in 146 requests
73.0 MBYour homepage downloads 73.0 MB in 146 requests on a phone: images 38.6 MB (54), media 33.3 MB (7) and scripts 740 KiB (44). Under 2 MB keeps phones on slow connections fast.
7 images over 500 KB
7 images weigh 36.2 MB together. On a phone connection a single image that size takes seconds.
7 images far larger than shown
33.5 MB7 images are downloaded at several times the size a phone draws them, for example hero_perrycounty-1.png at 3,300 px wide, shown at 300 px. Resized copies would save about 33.5 MB.
9 images in older formats
9 images (36.3 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.
8 images below the first screen load straight away
8 images further down the page (30.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 20.7 g of CO₂ per visit
20.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 20.69 g of CO₂e: 2482.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
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.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 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.
38 links without text
38 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3, h3 → h6 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (76 characters)
Your title is 76 characters, so Google will cut it off around 60: “Little Rock, AR Web Design and Marketing Agency: inthooz.com MASS ENTHUSIASM”.
4 H1 headlines
There are 4 <h1> headlines (“get more APPLICANTS”, “build a STRONGERBRAND” and “reach more CUSTOMERS”). One clear main headline is easier for people and search engines.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
56 internal links, 64 external
The homepage links to 56 pages on inthooz.com and 64 external pages.
6 checks passed
Meta description: 101 characters
Your meta description is 101 characters: “Create effective online and offline strategies with a digital marketing agency that delivers results.”.
Canonical URL set
The canonical URL is https://inthooz.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://inthooz.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://inthooz.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (990 words), so crawlers that don't run JavaScript still read it.
Other pages
14 pages without a meta description
https://inthooz.com/team, https://inthooz.com/news, https://inthooz.com/contact, https://inthooz.com/digital, https://inthooz.com/design and https://inthooz.com/marketing and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages without an H1
https://inthooz.com/encoreeducation, https://inthooz.com/case_study/weaver-bailey-contractors, https://inthooz.com/case_study/arkansas-public-defenders-commission, https://inthooz.com/case_study/arkansas-bone-joint, https://inthooz.com/case_study/moving-arkansas and https://inthooz.com/case_study/perry-county-arkansas and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://inthooz.com/case_study/arkansas-public-defenders-commission took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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
4 broken images
4 images failed to load on a phone, for example https://inthooz.com/.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
2 checks passed
Tap targets are thumb-sized
18 of 22 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
About 784 words of copy
The homepage carries about 784 words of visible text.
5 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact me” and “CONTACT”.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, 30 customer or partner logos and 4 trust badges.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 3 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta 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.
17 cookies set on arrival
17Opening the homepage sets 17 cookies, 4 of them by other companies (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.
22 other companies contacted
Loading the homepage contacts 22 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 inthooz.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
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics
- Hosting
- Liquid Web
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on inthooz.com, including 12 speed issues, 3 SEO issues and 2 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.