Website review, no card needed
andcompany.com website review
Visit site (opens in a new tab)Reviewed 21 October 202632 issues · 75 checks
This review found 32 issues worth fixing on andcompany.com, 11 of them high impact, across 75 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
74CClosest 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.6 s
1.1 s
1.7 s
2.3 s
2.8 s
3.4 s
4.0 s
4.6 s
Speed
Improve image delivery
1.1 s · 683 KiB14 images could be 683 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.7 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.
Reduce unused JavaScript
1.1 s · 137 KiBAbout 137 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 61
61/100Your mobile performance score is 61 (desktop: 68). Pages that score under 90 lose visitors before the first paint.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, jQuery CDN and ipmeta.io and others), adding 587 KiB and 252 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 14 KiB3 files are served with short cache lifetimes, so returning visitors download them again (14 KiB).
Reduce unused CSS
150 ms · 11 KiBAbout 11 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.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 127 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
1 checks passed
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 289 ms of it running JavaScript. That is comfortably low.
Core Web Vitals
Largest Contentful Paint: 7.3 s
7.3 sYour largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Time to Interactive: 7.3 s
7.3 sThe page becomes fully interactive after 7.3 s. Good is under 3.8 s.
1 image without width and height
1 image 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
Total Blocking Time: 101 ms
101 msScripts block the page for only 101 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.1 MB in 54 requests
3.1 MBYour homepage downloads 3.1 MB in 54 requests on a phone: images 2.4 MB (26), scripts 385 KiB (13) and fonts 233 KiB (6). Under 2 MB keeps phones on slow connections fast.
6 images below the first screen load straight away
6 images further down the page (448 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
5 images in older formats
5 images (428 KiB) 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 0.9 g of CO₂ per visit
0.87 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.87 g of CO₂e: 104.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
1 checks passed
13 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 17 WCAG 2.2 A/AA and best-practice rules on the phone render: 13 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (11 characters)
Your title is only 11 characters: “and company”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (61 characters)
Your meta description is only 61 characters: “We are an independently-owned, award-winning creative agency.”. 70 to 160 characters is enough to sell the click.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No XML sitemap
No XML sitemap at https://www.andcompany.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at andcompany.com/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
15 internal links, 3 external
The homepage links to 15 pages on andcompany.com and 3 external pages.
1 checks passed
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
AI search readiness
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://www.andcompany.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.
1 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Other pages
15 pages share a title
/, https://www.andcompany.com/case-study/josie-maran, https://www.andcompany.com/case-study/bmf, https://www.andcompany.com/case-study/blink-twice, https://www.andcompany.com/case-study/spotlight and https://www.andcompany.com/case-study/abigail and 9 others all use the title “and company”. Search engines can't tell which page to show for a search, so each competes with the others.
14 pages share a meta description
https://www.andcompany.com/case-study/josie-maran, https://www.andcompany.com/case-study/bmf, https://www.andcompany.com/case-study/blink-twice, https://www.andcompany.com/case-study/spotlight, https://www.andcompany.com/case-study/abigail and https://www.andcompany.com/case-study/painkiller and 8 others use the same meta description. A description written for each page earns more clicks.
14 pages without an H1
https://www.andcompany.com/case-study/josie-maran, https://www.andcompany.com/case-study/bmf, https://www.andcompany.com/case-study/blink-twice, https://www.andcompany.com/case-study/spotlight, https://www.andcompany.com/case-study/abigail and https://www.andcompany.com/case-study/painkiller and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
14 pages with very little text
https://www.andcompany.com/case-study/josie-maran, https://www.andcompany.com/case-study/bmf, https://www.andcompany.com/case-study/blink-twice, https://www.andcompany.com/case-study/spotlight, https://www.andcompany.com/case-study/abigail and https://www.andcompany.com/case-study/painkiller and 8 others 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.
4 pages slow to respond
https://www.andcompany.com/case-study/josie-maran, https://www.andcompany.com/case-study/blink-twice, https://www.andcompany.com/case-study/spotlight and https://www.andcompany.com/case-study/abigail took over 3 s to send their HTML from our server.
14 internal pages checked
We fetched 14 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 14 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.
2 checks passed
Tap targets are thumb-sized
14 of 14 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.
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.
Only about 85 words
The homepage has only about 85 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 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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
1 call to action
The homepage has 1 call to action, for example “Contact”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 2 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
8 other companies contacted
Loading the homepage contacts 8 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 andcompany.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on andcompany.com, including 9 speed issues, 7 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.