Website review, no card needed

solarisoffgrid.com logo

solarisoffgrid.com website review

Visit site (opens in a new tab)Reviewed 10 November 202622 issues · 70 checks

This review found 22 issues worth fixing on solarisoffgrid.com, 4 of them high impact, across 70 checks. The most urgent: 5 tap targets too small. 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 solarisoffgrid.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. solarisoffgrid.com at 0.4 s0.4 s
  2. solarisoffgrid.com at 0.8 s0.8 s
  3. solarisoffgrid.com at 1.1 s1.1 s
  4. solarisoffgrid.com at 1.5 s1.5 s
  5. solarisoffgrid.com at 1.9 s1.9 s
  6. solarisoffgrid.com at 2.3 s2.3 s
  7. solarisoffgrid.com at 2.7 s2.7 s
  8. solarisoffgrid.com at 3.1 s3.1 s

Speed

4 to fix96
  • 7 third-party services on the page

    7 third-party services load with your homepage (Wix, Hubspot and Google Tag Manager and others), adding 2.0 MB and 664 ms of main-thread time.

  • Wix adds 473 ms

    473 ms

    Wix costs a phone 473 ms of main-thread work and 1.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.

  • Main-thread work: 2.4 s

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

  • 2,069 HTML elements

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

  • Reduce unused JavaScript

    177 KiB

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

  • Use efficient cache lifetimes

    139 KiB

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

  • 3 long tasks on the main thread

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

  • Reduce unused CSS

    37 KiB

    About 37 KiB of CSS is downloaded but never applied on this page.

  • Duplicated JavaScript

    27 KiB

    27 KiB JavaScript is shipped twice across bundles.

  • Legacy JavaScript

    26 KiB

    Polyfills for old browsers add 26 KiB JavaScript that modern phones do not need.

  • Improve image delivery

    22 KiB

    1 image could be 22 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 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
  • Mobile performance score: 96

    96/100

    Your mobile performance score is 96. That is in Google's “good” band (90 and up).

  • Server response: 52 ms

    52 ms

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

Core Web Vitals

2 to fix98
  • Time to Interactive: 13.6 s

    13.6 s

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

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

4 checks passed
  • Largest Contentful Paint: 2.2 s

    2.2 s

    Your largest element renders in 2.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Climate resilience is constrained by inefficient capital fl…”.

  • Speed Index: 2.6 s

    2.6 s

    Visually, the page fills in at 2.6 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.054

    0.054

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

  • Total Blocking Time: 9 ms

    9 ms

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

Images and page weight

1 to fix85
  • Page weight: 3.2 MB in 220 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 220 requests on a phone: scripts 1.3 MB (103), other files 1.1 MB (88) and fonts 501 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.91 g

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

4 to fixGoogle 9294
  • 5 tap targets too small

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

  • 4 text elements with low contrast

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

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

  • 5 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 70 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

3 to fixGoogle 10086
  • 3 H1 headlines

    There are 3 <h1> headlines (“Fintech”, “infractructure for last-mile credit” and “Built to Scale”). One clear main headline is easier for people and search engines.

  • Meta description is long (296 characters)

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

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

  • 14 internal links, 64 external

    The homepage links to 14 pages on solarisoffgrid.com and 64 external pages.

5 checks passed
  • Title: 56 characters

    Your title is a healthy 56 characters: “Innovative solutions for Inclusive access | Masunga.tech”.

  • Canonical URL set

    The canonical URL is https://www.masunga.tech/.

  • 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.masunga.tech/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.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.masunga.tech/llms.txt (3 KiB, 3 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.masunga.tech/blog has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.masunga.tech/blog has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 internal page checked

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

5 checks passed
  • Linked pages load

    All 1 page 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.

  • Every page has a title

    All 1 page that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 8 small tap targets

    8 of 14 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 “globalThis.defineStrictProperty is not a function”.

1 checks passed
  • 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 457 words of copy

    The homepage carries about 457 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: “GET IN TOUCH”.

  • 1 call to action

    The homepage has 1 call to action, for example “GET IN TOUCH”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Tag Manager, HubSpot and LinkedIn Insight (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.

  • 17 cookies set on arrival

    17

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

  • 22 other companies contacted

    Loading the homepage contacts 22 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 solarisoffgrid.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
Wix
Analytics
Google Analytics
Hosting
OVHcloud

Hiring

Hiring
1 open role
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 22 issues on solarisoffgrid.com, including 6 speed issues, 3 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