Website review, no card needed

solutions2go.ca logo

solutions2go.ca website review

Visit site (opens in a new tab)Reviewed 19 November 202631 issues · 78 checks

This review found 31 issues worth fixing on solutions2go.ca, 11 of them high impact, across 78 checks. The most urgent: use efficient cache lifetimes. 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

Real-visitor load time (LCP)75th percentile, phones
2.1 s1.7 sMay 30Nov 141.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.8 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20262.0 s
Jun 27, 20261.9 s
Jul 4, 20261.8 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.0 s
Oct 31, 20262.0 s
Nov 7, 20261.8 s
Nov 14, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
84 ms68 msMay 30Nov 1476 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202677 ms
Jun 6, 202679 ms
Jun 13, 202678 ms
Jun 20, 202679 ms
Jun 27, 202679 ms
Jul 4, 202676 ms
Jul 11, 202676 ms
Jul 18, 202682 ms
Jul 25, 202681 ms
Aug 1, 202681 ms
Aug 8, 202681 ms
Aug 15, 202671 ms
Aug 22, 202673 ms
Aug 29, 202670 ms
Sep 5, 202672 ms
Sep 12, 202678 ms
Sep 19, 202675 ms
Sep 26, 202676 ms
Oct 3, 202676 ms
Oct 10, 202673 ms
Oct 17, 202675 ms
Oct 24, 202673 ms
Oct 31, 202677 ms
Nov 7, 202676 ms
Nov 14, 202676 ms

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

Full-page screenshot of solutions2go.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. solutions2go.ca at 0.5 s0.5 s
  2. solutions2go.ca at 1.0 s1.0 s
  3. solutions2go.ca at 1.5 s1.5 s
  4. solutions2go.ca at 2.0 s2.0 s
  5. solutions2go.ca at 2.5 s2.5 s
  6. solutions2go.ca at 2.9 s2.9 s
  7. solutions2go.ca at 3.4 s3.4 s
  8. solutions2go.ca at 3.9 s3.9 s

Speed

6 to fix68
  • Use efficient cache lifetimes

    3.3 s · 1.9 MB

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

  • Improve image delivery

    2.3 s · 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 2.3 s faster on a phone.

  • Mobile performance score: 68

    68/100

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

  • Reduce unused JavaScript

    610 ms · 111 KiB

    About 111 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 610 ms faster on a phone.

  • Render-blocking requests

    600 ms

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

  • Font display

    300 ms

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

  • Minify JavaScript

    150 ms · 23 KiB

    23 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    150 ms · 23 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 254 KiB and 91 ms of main-thread time.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 55 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.

2 checks passed
  • Main-thread work: 0.3 s

    A phone's processor spends 0.3 s on main-thread work while loading, 142 ms of it running JavaScript. That is comfortably low.

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

8 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Largest Contentful Paint: 9.5 s

    9.5 s

    Your largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Airplane flying”.

  • Time to Interactive: 9.6 s

    9.6 s

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

  • Speed Index: 6.2 s

    6.2 s

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

  • Real-user LCP: 2.7 s

    2.7 s

    Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user TTFB: 1.1 s

    1.1 s

    Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • 11 images without width and height

    11 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -3%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 77 ms to 76 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +2%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user INP: 75 ms

    75 ms

    Real visitors wait 75 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.7 s

    1.7 s

    Real visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 5 ms

    5 ms

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

Images and page weight

5 to fix33
  • 1 image over 500 KB

    solutions2go_introducing_new_product_line.jpg weighs 734 KiB. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    983 KiB

    4 images are downloaded at several times the size a phone draws them, for example solutions2go_introducing_new_product_line.jpg at 1,400 px wide, shown at 300 px. Resized copies would save about 983 KiB.

  • Page weight: 2.3 MB in 19 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 19 requests on a phone: images 1.9 MB (8), scripts 258 KiB (3) and fonts 89 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 4 images in older formats

    4 images (1.5 MB) 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.

  • 3 images below the first screen load straight away

    3 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.6 g of CO₂ per visit

    0.64 g

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

Accessibility

1 to fixGoogle 9698
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 1 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 8586
  • No structured data

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

  • No XML sitemap

    No XML sitemap at https://www.solutions2go.ca/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at solutions2go.ca/robots.txt, the first file search crawlers ask for.

  • 11 links with vague text

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

  • 46 internal links, 1 external

    The homepage links to 46 pages on solutions2go.ca and 1 external page.

5 checks passed
  • Meta description: 94 characters

    Your meta description is 94 characters: “We are committed to Moving Distribution Forward, delivering innovative distribution solutions.”.

  • One H1 headline

    Your main headline reads: “Solutions 2 GOYour partner in Global Distribution Solutions”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Solutions 2 GO - Your partner in Global Distribution Solutions”.

  • Canonical URL set

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

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

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

1 checks passed
  • Text is in the HTML

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

Other pages

2 to fix88
  • 1 page points its canonical at the homepage

    https://www.solutions2go.ca/about.html declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 12 pages share a meta description

    https://www.solutions2go.ca/about.html, https://www.solutions2go.ca/solutions.html, https://www.solutions2go.ca/case-studies, https://www.solutions2go.ca/ProtectionPro.html, https://www.solutions2go.ca/contacts.html and https://www.solutions2go.ca/case-studies/ark-survival-evolved.html and 6 others use the same meta description. A description written for each page earns more clicks.

  • 1 page with very little text

    https://www.solutions2go.ca/ProtectionPro.html has 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.

  • 1 page slow to respond

    https://www.solutions2go.ca/privacy-policy.html took over 3 s to send its HTML from our server.

  • 12 internal pages checked

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

6 checks passed
  • Linked pages load

    All 12 pages we checked loaded without an error.

  • Every page has a meta description

    All 12 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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 12 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 12 small tap targets

    12 of 25 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

2 to fix70
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

    The homepage carries about 286 words of visible text.

3 checks passed
  • Clear next step on the first screen

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

  • 3 calls to action

    The homepage has 3 calls to action, for example “Learn more”, “Learn more about our services” and “Order online”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 2 cookies set on arrival

    2

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 solutions2go.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
Azure

Hiring

Hiring
7 open roles
Job board
careers page

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on solutions2go.ca, including 14 speed issues, 4 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