Website review, no card needed
adezignstudio.com website review
Visit site (opens in a new tab)Reviewed 4 November 202634 issues · 75 checks
This review found 34 issues worth fixing on adezignstudio.com, 7 of them high impact, across 75 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
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
Reduce unused JavaScript
2.4 s · 522 KiBAbout 522 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Use efficient cache lifetimes
1.2 s · 217 KiB7 files are served with short cache lifetimes, so returning visitors download them again (217 KiB).
Render-blocking requests
1.2 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Mobile performance score: 58
58/100Your mobile performance score is 58. 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 (Squarespace, Adobe TypeKit and sqspcdn.com and others), adding 1.9 MB and 795 ms of main-thread time.
Squarespace adds 788 ms
788 msSquarespace costs a phone 788 ms of main-thread work and 1.0 MB 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
450 ms · 76 KiBAbout 76 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 396 ms. During a long task the page ignores taps.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 743 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
squarespace-cdn.com adds 0 ms
0 mssquarespace-cdn.com costs a phone 0 ms of main-thread work and 870 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
200 ms · 32 KiBPolyfills for old browsers add 32 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Improve image delivery
227 KiB4 images could be 227 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 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
Server response: 24 ms
24 msYour server sent the HTML in 24 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.7 s
9.7 sYour largest element takes 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “I am a creative designer, entrepreneur, photographer and re…”.
Time to Interactive: 9.8 s
9.8 sThe page becomes fully interactive after 9.8 s. Good is under 3.8 s.
Total Blocking Time: 470 ms
470 msScripts block taps and scrolling for 470 ms in total while the page loads. Good is under 200 ms.
Speed Index: 5.0 s
5.0 sVisually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.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.
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: 2.1 MB in 47 requests
2.1 MBYour homepage downloads 2.1 MB in 47 requests on a phone: scripts 991 KiB (24), images 763 KiB (5) and fonts 146 KiB (7). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (189 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.59 g of CO₂e: 71.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
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.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 5 images in the HTML carry an alt attribute.
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 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
Title is short (23 characters)
Your title is only 23 characters: “Adezign | Anna Brackett”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (56 characters)
Your meta description is only 56 characters: “Creative designer, photographer, and real estate broker.”. 70 to 160 characters is enough to sell the click.
5 H1 headlines
There are 5 <h1> headlines (“Hello! I'm Anna Brackett.”, “Get to know me…” and “Creative”). One clear main headline is easier for people and search engines.
Structured data has 2 problems
Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/584e3d3e414fb5fd290…”.
22 internal links, 13 external
The homepage links to 22 pages on adezignstudio.com and 13 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.adezignstudio.com/.
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://www.adezignstudio.com/sitemap.xml.
AI search readiness
Organization data is thin (0 of 6 facts)
Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.adezignstudio.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
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Other pages
1 linked page is broken
Your homepage links to https://www.adezignstudio.com/coming-soon, which answers with an error. Visitors hit a dead end and search engines drop it.
5 pages without a meta description
https://www.adezignstudio.com/creative, https://www.adezignstudio.com/photography, https://www.adezignstudio.com/video, https://www.adezignstudio.com/contact and https://www.adezignstudio.com/terms-of-use have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.adezignstudio.com/creative, https://www.adezignstudio.com/photography and https://www.adezignstudio.com/video have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages with very little text
https://www.adezignstudio.com/creative, https://www.adezignstudio.com/photography, https://www.adezignstudio.com/video, https://www.adezignstudio.com/aboutanna and https://www.adezignstudio.com/contact 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.
7 internal pages checked
We fetched 7 pages linked from your homepage and read each the way a search engine does.
4 checks passed
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 6 pages that loaded have a <title>.
Best practices
7 small tap targets
7 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/sitecss/584e3d3e414fb5fd290549ec/72/55f0aac0e4b0f0a…”.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 106 words
The homepage has only about 106 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
2 calls to action
The homepage has 2 calls to action, for example “Contact”.
1 short form
A short form (1 field at most) is right on the homepage.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Ads (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.
4 cookies set on arrival
4Opening the homepage sets 4 cookies, 1 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.
13 other companies contacted
Loading the homepage contacts 13 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 adezignstudio.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
- Squarespace
- Hosting
- Squarespace
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on adezignstudio.com, including 16 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.