Website review, no card needed

outcodesoftware.com logo

outcodesoftware.com website review

Visit site (opens in a new tab)Reviewed 21 October 202642 issues · 81 checks

This review found 42 issues worth fixing on outcodesoftware.com, 15 of them high impact, across 81 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 outcodesoftware.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. outcodesoftware.com at 0.8 s0.8 s
  2. outcodesoftware.com at 1.7 s1.7 s
  3. outcodesoftware.com at 2.5 s2.5 s
  4. outcodesoftware.com at 3.3 s3.3 s
  5. outcodesoftware.com at 4.2 s4.2 s
  6. outcodesoftware.com at 5.0 s5.0 s
  7. outcodesoftware.com at 5.8 s5.8 s
  8. outcodesoftware.com at 6.7 s6.7 s

Speed

12 to fix45
  • Reduce unused JavaScript

    8.0 s · 1.6 MB

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

  • Render-blocking requests

    4.2 s

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

  • Google CDN adds 1.2 s

    1.2 s

    Google CDN costs a phone 1.2 s of main-thread work and 2.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 45

    45/100

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

  • Main-thread work: 6.9 s

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

  • 8 third-party services on the page

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

  • Use efficient cache lifetimes

    600 ms · 251 KiB

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

  • Google Tag Manager adds 437 ms

    437 ms

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

  • website-files.com adds 266 ms

    266 ms

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

  • Facebook adds 306 ms

    306 ms

    Facebook costs a phone 306 ms of main-thread work and 223 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.

  • 20 long tasks on the main thread

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

  • 1,855 HTML elements

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

  • Improve image delivery

    199 KiB

    3 images could be 199 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    150 ms · 12 KiB

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

  • Reduce unused CSS

    52 KiB

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

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

    21 ms

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

Core Web Vitals

6 to fix55
  • First Contentful Paint: 14.6 s

    14.6 s

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

  • Largest Contentful Paint: 18.5 s

    18.5 s

    Your largest element takes 18.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “SRVD project”.

  • Time to Interactive: 29.9 s

    29.9 s

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

  • Speed Index: 14.6 s

    14.6 s

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

  • Total Blocking Time: 431 ms

    431 ms

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

  • 25 images without width and height

    25 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
  • Cumulative Layout Shift: 0.021

    0.021

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

Images and page weight

3 to fix53
  • Page weight: 5.8 MB in 120 requests

    5.8 MB

    Your homepage downloads 5.8 MB in 120 requests on a phone: scripts 3.3 MB (34), other files 1.1 MB (31) and images 592 KiB (28). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    6601dc7c5b4df6025879860e_Frame 3886.webp 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

    164 KiB

    2 images are downloaded at several times the size a phone draws them, for example 6601dc7c5b4df6025879860e_Frame 3886.webp at 1,248 px wide, shown at 259 px. Resized copies would save about 164 KiB.

  • About 1.7 g of CO₂ per visit

    1.66 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

6 to fixGoogle 9192
  • Unlabelled dropdowns

    1 dropdown has no label.

  • 5 text elements with low contrast

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

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

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

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

  • 22 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 277 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

7 to fixGoogle 8267
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (4 characters)

    Your title is only 4 characters: “Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

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

  • 18 links with vague text

    18 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 incomplete here.

  • 84 internal links, 3 external

    The homepage links to 84 pages on outcodesoftware.com and 3 external pages.

2 checks passed
  • One H1 headline

    Your main headline reads: “Product focused software development.”.

  • robots.txt in place

    robots.txt is in place.

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.outcodesoftware.com/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 (2,330 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix63
  • 1 linked page is broken

    Your homepage links to https://www.outcodesoftware.com/contact-us, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 8 pages share a title

    https://www.outcodesoftware.com/engineering/e-commerce, https://www.outcodesoftware.com/engineering/dedicated-resources, https://www.outcodesoftware.com/engineering/mobile-app-development, https://www.outcodesoftware.com/engineering/software-application-development, https://www.outcodesoftware.com/engineering/low-code-cms-development and https://www.outcodesoftware.com/engineering/dev-ops and 2 others all use the title “Outcode Software”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages without a meta description

    https://www.outcodesoftware.com/services, https://www.outcodesoftware.com/blog, https://www.outcodesoftware.com/about-us, https://www.outcodesoftware.com/contact, https://www.outcodesoftware.com/our-services/engineering and https://www.outcodesoftware.com/engineering/e-commerce and 8 others 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 30 found) and read each the way a search engine does.

4 checks passed
  • 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 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Unexpected token '<'”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

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

6 checks passed
  • 22 calls to action

    The homepage has 22 calls to action, for example “Contact Us” and “Learn more”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 13 testimonial or review blocks, 144 customer or partner logos and 10 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and LinkedIn Insight.

  • Direct contact links

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

  • 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, LinkedIn Insight 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.

  • 8 cookies set on arrival

    8

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

  • 30 other companies contacted

    Loading the homepage contacts 30 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 outcodesoftware.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 © 2024.

Stack

CMS
Webflow
Analytics
Google Analytics | Google Tag Manager

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 outcodesoftware.com, including 18 speed issues, 7 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