Website review, no card needed

attractionstudio.co.nz logo

attractionstudio.co.nz website review

Visit site (opens in a new tab)Reviewed 6 November 202633 issues · 71 checks

This review found 33 issues worth fixing on attractionstudio.co.nz, 8 of them high impact, across 71 checks. The most urgent: page weight: 12.8 MB in 68 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of attractionstudio.co.nz (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. attractionstudio.co.nz at 0.4 s0.4 s
  2. attractionstudio.co.nz at 0.8 s0.8 s
  3. attractionstudio.co.nz at 1.1 s1.1 s
  4. attractionstudio.co.nz at 1.5 s1.5 s
  5. attractionstudio.co.nz at 1.9 s1.9 s
  6. attractionstudio.co.nz at 2.3 s2.3 s
  7. attractionstudio.co.nz at 2.6 s2.6 s
  8. attractionstudio.co.nz at 3.0 s3.0 s

Speed

11 to fix48
  • Render-blocking requests

    1.0 s

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.

  • Mobile performance score: 48

    48/100

    Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Use efficient cache lifetimes

    300 ms · 10.1 MB

    9 files are served with short cache lifetimes, so returning visitors download them again (10.1 MB).

  • 8 third-party services on the page

    8 third-party services load with your homepage (elfsightcdn.com, Google Tag Manager and website-files.com and others), adding 12.5 MB and 1.9 s of main-thread time.

  • Improve image delivery

    300 ms · 1.1 MB

    7 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • website-files.com adds 262 ms

    262 ms

    website-files.com costs a phone 262 ms of main-thread work and 11.4 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.

  • elfsightcdn.com adds 956 ms

    956 ms

    elfsightcdn.com costs a phone 956 ms of main-thread work and 466 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 JavaScript

    447 KiB

    About 447 KiB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 401 ms

    401 ms

    Google Tag Manager costs a phone 401 ms of main-thread work and 343 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.

  • 10 long tasks on the main thread

    10 long tasks block the main thread while loading, the longest for 389 ms. During a long task the page ignores taps.

  • Main-thread work: 3.4 s

    A phone's processor spends 3.4 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Reduce unused CSS

    150 ms · 33 KiB

    About 33 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.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    13 KiB

    Polyfills for old browsers add 13 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.

1 checks passed
  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix47
  • Time to Interactive: 17.0 s

    17.0 s

    The page becomes fully interactive after 17.0 s. Good is under 3.8 s.

  • Largest Contentful Paint: 5.6 s

    5.6 s

    Your largest element takes 5.6 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.9 s

    7.9 s

    Visually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 809 ms

    809 ms

    Scripts block taps and scrolling for 809 ms in total while the page loads. Good is under 200 ms.

  • Cumulative Layout Shift: 0.11

    0.11

    The layout shifts by 0.11 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 13 images without width and height

    13 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.

1 checks passed
  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

Images and page weight

3 to fix53
  • Page weight: 12.8 MB in 68 requests

    12.8 MB

    Your homepage downloads 12.8 MB in 68 requests on a phone: media 9.5 MB (2), images 1.4 MB (13) and scripts 1.2 MB (15). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    6634637a664a763a7e24db6d_attraction-studio-project-irelands- is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 2 images far larger than shown

    154 KiB

    2 images are downloaded at several times the size a phone draws them, for example 65c44456dac9f1cb14240524_Attraction-Studio-WebIcon-About.png at 500 px wide, shown at 110 px. Resized copies would save about 154 KiB.

  • 3 images in older formats

    3 images (368 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 3.6 g of CO₂ per visit

    3.62 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.62 g of CO₂e: 434.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

3 to fixGoogle 9496
  • All page content should be contained by landmarks (37 elements)

    All page content should be contained by landmarks: 37 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.

  • 3 links without text

    3 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed
  • Every image has alt text

    All 28 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10084
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (170 characters)

    Your meta description is 170 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 31 internal links, 5 external

    The homepage links to 31 pages on attractionstudio.co.nz and 5 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Take your brand to a better place”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “Attraction Studio | Christchurch Branding Agency”.

  • 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.attractionstudio.co.nz/sitemap.xml.

AI search readiness

1 to fix88
  • 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.attractionstudio.co.nz/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.

2 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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (552 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 2 pages share a title

    https://www.attractionstudio.co.nz/additional/terms-and-conditions and https://www.attractionstudio.co.nz/additional/privacy-policy all use the title “Attraction Studio”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.attractionstudio.co.nz/additional/terms-and-conditions and https://www.attractionstudio.co.nz/additional/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages with very little text

    https://www.attractionstudio.co.nz/all-work, https://www.attractionstudio.co.nz/news and https://www.attractionstudio.co.nz/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.

  • 13 internal pages checked

    We fetched 13 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 13 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 an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10092
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80
  • 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.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 715 words of copy

    The homepage carries about 715 words of visible text.

4 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Register Now” and “Contact”.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 20 other companies contacted

    Loading the homepage contacts 20 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 attractionstudio.co.nz, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2024.

Stack

CMS
Webflow
Analytics
Google Tag Manager
Hosting
Webflow

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 attractionstudio.co.nz, including 17 speed issues, 4 SEO issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25