Website review, no card needed

avartphotography.ca logo

avartphotography.ca website review

Visit site (opens in a new tab)Reviewed 12 November 202638 issues · 78 checks

This review found 38 issues worth fixing on avartphotography.ca, 14 of them high impact, across 78 checks. The most urgent: reduce unused JavaScript. 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 avartphotography.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix54
  • Reduce unused JavaScript

    2.5 s · 488 KiB

    About 488 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.

  • Render-blocking requests

    2.5 s

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

  • Improve image delivery

    450 ms · 1.7 MB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (pixpa.com, Google Tag Manager and Vimeo and others), adding 8.8 MB and 686 ms of main-thread time.

  • Reduce unused CSS

    820 ms · 211 KiB

    About 211 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 820 ms faster on a phone.

  • Mobile performance score: 54

    54/100

    Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.

  • pixpa.com adds 397 ms

    397 ms

    pixpa.com costs a phone 397 ms of main-thread work and 5.6 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.

  • Use efficient cache lifetimes

    800 ms · 143 KiB

    8 files are served with short cache lifetimes, so returning visitors download them again (143 KiB).

  • Vimeo adds 134 ms

    134 ms

    Vimeo costs a phone 134 ms of main-thread work and 3.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.

  • Main-thread work: 2.1 s

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

  • 1,752 HTML elements

    The page has 1,752 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 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: 59 ms

    59 ms

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

Core Web Vitals

5 to fix64
  • Largest Contentful Paint: 15.9 s

    15.9 s

    Your largest element takes 15.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “AVArt Photography”.

  • First Contentful Paint: 6.5 s

    6.5 s

    The first text or image appears after 6.5 s on a phone. Good is under 1.8 s.

  • Time to Interactive: 16.0 s

    16.0 s

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

  • Speed Index: 8.8 s

    8.8 s

    Visually, the page fills in at 8.8 s (Speed Index). Good is under 3.4 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: 176 ms

    176 ms

    Scripts block the page for only 176 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix47
  • Page weight: 8.9 MB in 129 requests

    8.9 MB

    Your homepage downloads 8.9 MB in 129 requests on a phone: images 4.9 MB (24), other files 2.4 MB (29) and scripts 1.1 MB (46). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    czM6Ly9waXhwYS10ZXN0L2NvbS9sYXJnZS83OTQ3MTYvNzk0NzE2LTE3NzY3 weighs 515 KiB. On a phone connection a single image that size takes seconds.

  • An image on the first screen is lazy-loaded

    czM6Ly9waXhwYS10ZXN0L2NvbS9sYXJnZS83OTQ3MTYvNzk0NzE2LTE3NzY3 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).

  • About 2.5 g of CO₂ per visit

    2.52 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.52 g of CO₂e: 302.8 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

6 to fixGoogle 9692
  • 2 text elements with low contrast

    2 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 (10 elements)

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

2 to fixGoogle 10083
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (75 characters)

    Your title is 75 characters, so Google will cut it off around 60: “AVArt Photography | Newborn Photographer in Calgary, AB | AVArt Photography”.

  • 40 internal links, 9 external

    The homepage links to 40 pages on avartphotography.ca and 9 external pages.

6 checks passed
  • Meta description: 119 characters

    Your meta description is 119 characters: “Welcome to AVArt Photography, your premier choice for capturing precious newborn and milestones moments in Calgary, AB.”.

  • Canonical URL set

    The canonical URL is https://www.avartphotography.ca/.

  • Structured data in place

    Structured data found: 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://www.avartphotography.ca/sitemap.xml.

AI search readiness

2 to fix53
  • robots.txt blocks 2 AI answer engine crawlers

    2 of 6

    Your robots.txt shuts out ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • 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.avartphotography.ca/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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

1 checks passed
  • Text is in the HTML

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

Other pages

3 to fix75
  • 7 pages without a title

    https://www.avartphotography.ca/getjsassets, https://www.avartphotography.ca/portfolio/milestones-gallery, https://www.avartphotography.ca/portfolio/christmas-gallery, https://www.avartphotography.ca/portfolio/family, https://www.avartphotography.ca/portfolio/maternity-photoshoots and https://www.avartphotography.ca/investments and 1 other have no <title>, so Google invents the link text in results.

  • 7 pages without a meta description

    https://www.avartphotography.ca/getjsassets, https://www.avartphotography.ca/portfolio/milestones-gallery, https://www.avartphotography.ca/portfolio/christmas-gallery, https://www.avartphotography.ca/portfolio/family, https://www.avartphotography.ca/portfolio/maternity-photoshoots and https://www.avartphotography.ca/investments and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://www.avartphotography.ca/getjsassets, https://www.avartphotography.ca/portfolio/newborn-gallery, https://www.avartphotography.ca/portfolio/milestones-gallery, https://www.avartphotography.ca/portfolio/christmas-gallery, https://www.avartphotography.ca/portfolio/family and https://www.avartphotography.ca/portfolio/maternity-photoshoots and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.avartphotography.ca/portfolio/newborn-gallery and https://www.avartphotography.ca/portfolio/blossoms 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.

  • 11 internal pages checked

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

4 checks passed
  • Linked pages load

    All 11 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.

Best practices

3 to fixGoogle 5888
  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    5 of 5 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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.

  • Thin social proof

    Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 2,655 words of copy

    The homepage carries about 2,655 words of visible text.

4 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Buy Image”, “BOOK A SESSION” and “CONTACT”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies, 3 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.

  • 15 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Analytics
Hosting
AWS

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on avartphotography.ca, including 16 speed issues, 2 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

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