Website review, no card needed
craftsmanplus.com website review
Visit site (opens in a new tab)Reviewed 22 October 202627 issues · 75 checks
This review found 27 issues worth fixing on craftsmanplus.com, 6 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.0 s |
| May 9, 2026 | 1.0 s |
| May 16, 2026 | 952 ms |
| May 23, 2026 | 1.1 s |
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.7 s
1.5 s
2.2 s
2.9 s
3.6 s
4.4 s
5.1 s
5.8 s
Speed
Improve image delivery
1.1 s · 3.3 MB17 images could be 3.3 MB 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.6 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 60
60/100Your mobile performance score is 60 (desktop: 95). Pages that score under 90 lose visitors before the first paint.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, ContentSquare and Google Analytics and others), adding 684 KiB and 621 ms of main-thread time.
Google Tag Manager adds 474 ms
474 msGoogle Tag Manager costs a phone 474 ms of main-thread work and 433 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.
Reduce unused CSS
300 ms · 27 KiBAbout 27 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Reduce unused JavaScript
304 KiBAbout 304 KiB of JavaScript is downloaded but never used on this page.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 865 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,811 HTML elements
The page has 1,811 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify CSS
150 ms · 18 KiB18 KiB could be saved by minifying CSS.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 148 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
19 KiB2 files are served with short cache lifetimes, so returning visitors download them again (19 KiB).
Phones get a much slower page than desktops
Desktop scores 95 but mobile only 60. A gap that wide usually means heavy scripts and images that hit phones hardest.
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
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.5 s
6.5 sYour largest element takes 6.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: 7.8 s
7.8 sThe page becomes fully interactive after 7.8 s. Good is under 3.8 s.
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
41 images without width and height
41 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Total Blocking Time: 386 ms
386 msScripts block taps and scrolling for 386 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.4 MB in 109 requests
5.4 MBYour homepage downloads 5.4 MB in 109 requests on a phone: images 4.7 MB (92), scripts 643 KiB (9) and fonts 48 KiB (2). Under 2 MB keeps phones on slow connections fast.
6 images in older formats
6 images (658 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.
2 images far larger than shown
149 KiB2 images are downloaded at several times the size a phone draws them, for example hero-main.png at 1,440 px wide, shown at 302 px. Resized copies would save about 149 KiB.
About 1.5 g of CO₂ per visit
1.53 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.53 g of CO₂e: 184.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
16 text elements with low contrast
16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (18 elements)
ARIA role should be appropriate for the element: 18 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 571 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
18 links with vague text
18 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
41 internal links, 15 external
The homepage links to 41 pages on craftsmanplus.com and 15 external pages.
8 checks passed
Meta description: 143 characters
Your meta description is 143 characters: “CRAFTSMAN+ is the AI infrastructure for high-volume creative. Build, optimise, and scale playable and HTML5 ads with pe…”.
One H1 headline
Your main headline reads: “Build Ads with Intelligence”.
Title: 40 characters
Your title is a healthy 40 characters: “CRAFTSMAN+ | Build Ads with Intelligence”.
Canonical URL set
The canonical URL is https://craftsmanplus.com/.
Structured data in place
Structured data found: BreadcrumbList, FAQPage, Organization, SoftwareApplication and WebPage.
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://craftsmanplus.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://craftsmanplus.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 (679 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://craftsmanplus.com/platform, https://craftsmanplus.com/solutions, https://craftsmanplus.com/services, https://craftsmanplus.com/blog, https://craftsmanplus.com/about-us and https://craftsmanplus.com/book-a-demo and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://craftsmanplus.com/platform has no <h1> headline, so visitors and search engines get no clear main topic.
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
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 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 960 words of copy
The homepage carries about 960 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book a Demo”.
9 calls to action
The homepage has 9 calls to action, for example “Book a Demo” and “Learn More”.
Social proof on the page
Social proof on the homepage: 6 testimonial or review blocks, 260 customer or partner logos and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, 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.
8 cookies set on arrival
8Opening the homepage sets 8 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 craftsmanplus.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
Hiring
- Hiring
- 2 open roles
- Teams
- Creative (1), Marketing (1)
- Job board
- greenhouse
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on craftsmanplus.com, including 15 speed issues, 1 SEO issue 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.