Website review, no card needed

accnetinc.com logo

accnetinc.com website review

Visit site (opens in a new tab)Reviewed 8 November 202642 issues · 87 checks

This review found 42 issues worth fixing on accnetinc.com, 14 of them high impact, across 87 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 accnetinc.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. accnetinc.com at 1.6 s1.6 s
  2. accnetinc.com at 3.1 s3.1 s
  3. accnetinc.com at 4.7 s4.7 s
  4. accnetinc.com at 6.2 s6.2 s
  5. accnetinc.com at 7.8 s7.8 s
  6. accnetinc.com at 9.4 s9.4 s
  7. accnetinc.com at 10.9 s10.9 s
  8. accnetinc.com at 12.5 s12.5 s

Speed

13 to fix44
  • Reduce unused JavaScript

    6.3 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.3 s faster on a phone.

  • Render-blocking requests

    2.8 s

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

  • Mobile performance score: 44

    44/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and Hotjar and others), adding 2.7 MB and 1.3 s of main-thread time.

  • Use efficient cache lifetimes

    850 ms · 156 KiB

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

  • Reduce unused CSS

    750 ms · 143 KiB

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

  • Google Tag Manager adds 542 ms

    542 ms

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

  • Google CDN adds 375 ms

    375 ms

    Google CDN costs a phone 375 ms of main-thread work and 1.1 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.

  • Improve image delivery

    150 ms · 313 KiB

    2 images could be 313 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Main-thread work: 3.9 s

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

  • Legacy JavaScript

    300 ms · 37 KiB

    Polyfills for old browsers add 37 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • Minify JavaScript

    300 ms · 28 KiB

    28 KiB could be saved by minifying JavaScript.

  • tidio.co adds 66 ms

    66 ms

    tidio.co costs a phone 66 ms of main-thread work and 515 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.

  • 17 long tasks on the main thread

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

  • 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: 43 ms

    43 ms

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

Core Web Vitals

7 to fix53
  • Largest Contentful Paint: 23.5 s

    23.5 s

    Your largest element takes 23.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AccNet Accounting We are Tax Professionals who help our cli…”. Most of its time is resource load delay (10.2 s).

  • Speed Index: 22.4 s

    22.4 s

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

  • Time to Interactive: 26.0 s

    26.0 s

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

  • First Contentful Paint: 5.1 s

    5.1 s

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

  • Total Blocking Time: 348 ms

    348 ms

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

  • Cumulative Layout Shift: 0.117

    0.117

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

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

Images and page weight

1 to fix70
  • Page weight: 13.1 MB in 124 requests

    13.1 MB

    Your homepage downloads 13.1 MB in 124 requests on a phone: media 6.6 MB (4), scripts 2.8 MB (55) and images 2.6 MB (10). Under 2 MB keeps phones on slow connections fast.

  • About 3.7 g of CO₂ per visit

    3.71 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

10 to fixGoogle 8387
  • 14 text elements with low contrast

    14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Links must have discernible text (5 elements)

    Links must have discernible text: 5 elements on the page fail this check, rated serious by axe-core.

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

  • All page content should be contained by landmarks (23 elements)

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h4, h1 → h4 and h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Title is long (88 characters)

    Your title is 88 characters, so Google will cut it off around 60: “Professional Accounting Services Accnet Accounting Network - File your Tax Return Canada”.

  • 16 H1 headlines

    There are 16 <h1> headlines (“AccNet Accounting”, “AccNet Accounting” and “ARE YOU ELIGIBLE FOR A COMPLIMENTARY TAX REVIEW?”). One clear main headline is easier for people and search engines.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 47 internal links, 12 external

    The homepage links to 47 pages on accnetinc.com and 12 external pages.

6 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “Are you looking for an experienced accountant to assist you with filing your tax return this year? Visit our website to…”.

  • Canonical URL set

    The canonical URL is https://accnetinc.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, Place, WebPage and 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://accnetinc.com/sitemap_index.xml.

AI search readiness

100
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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://accnetinc.com/corporate-tax-accounting is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 6 pages without a meta description

    https://accnetinc.com/hempco-canada-case-study, https://accnetinc.com/bc-ltd-case-study, https://accnetinc.com/blog, https://accnetinc.com/terms-of-service, https://accnetinc.com/privacy-policy and https://accnetinc.com/corporate-tax-accounting have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    10 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

4 to fixGoogle 7769
  • 3 broken images

    3 images failed to load on a phone, for example https://accnetinc.com/wp-content/uploads/2019/04/accnet-logo-final-01.svg.

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 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.”).

  • 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_TUNNEL_CONNECTION_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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 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 1,127 words of copy

    The homepage carries about 1,127 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact”, “Book an appointment with us” and “BOOK A COMPLIMENTARY BUSINESS TAX REVIEW”.

  • 2 short forms

    2 short forms (5 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 56 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 2 email links.

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 9 cookies set on arrival

    9

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

  • 16 other companies contacted

    Loading the homepage contacts 16 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 accnetinc.com, 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 © 2020.

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager
Hosting
Idigital Internet Inc.

Company

Headquarters
North Vancouver

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on accnetinc.com, including 20 speed issues, 3 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