Website review, no card needed

saaspack.com logo

saaspack.com website review

Visit site (opens in a new tab)Reviewed 8 November 202632 issues · 79 checks

This review found 32 issues worth fixing on saaspack.com, 12 of them high impact, across 79 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

Full-page screenshot of saaspack.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. saaspack.com at 0.4 s0.4 s
  2. saaspack.com at 0.9 s0.9 s
  3. saaspack.com at 1.3 s1.3 s
  4. saaspack.com at 1.7 s1.7 s
  5. saaspack.com at 2.1 s2.1 s
  6. saaspack.com at 2.6 s2.6 s
  7. saaspack.com at 3.0 s3.0 s
  8. saaspack.com at 3.4 s3.4 s

Speed

5 to fix71
  • Use efficient cache lifetimes

    1.1 s · 2.1 MB

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

  • Render-blocking requests

    1.8 s

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

  • Mobile performance score: 71

    71/100

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

  • Reduce unused JavaScript

    450 ms · 390 KiB

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

  • Google Maps adds 159 ms

    159 ms

    Google Maps costs a phone 159 ms of main-thread work and 483 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Maps, Google Tag Manager and Google Fonts and others), adding 847 KiB and 280 ms of main-thread time.

  • Minify JavaScript

    150 ms · 24 KiB

    24 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    144 KiB

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

  • Font display

    100 ms

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

  • 2 long tasks on the main thread

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

  • Improve image delivery

    18 KiB

    1 image could be 18 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
  • Main-thread work: 1.1 s

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

  • Server response: 106 ms

    106 ms

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

Core Web Vitals

5 to fix75
  • Time to Interactive: 10.9 s

    10.9 s

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

  • Largest Contentful Paint: 5.1 s

    5.1 s

    Your largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “It's time to Transform your Business Process”.

  • Speed Index: 6.4 s

    6.4 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • 19 images without width and height

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

2 checks passed
  • Cumulative Layout Shift: 0.046

    0.046

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

  • Total Blocking Time: 29 ms

    29 ms

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

Images and page weight

1 to fix67
  • Page weight: 3.1 MB in 102 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 102 requests on a phone: images 1.6 MB (19), scripts 950 KiB (42) and fonts 363 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.88 g

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

Accessibility

8 to fixGoogle 8389
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 9 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 9 links without text

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

  • 6 form fields without a label

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

  • Page language is “zxx”

    The page declares lang=“zxx”, which is not a usable language code (“zxx” means “no linguistic content”), so screen readers and translation tools guess.

  • Headings skip levels

    Headings skip levels (h2 → h5, 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 44 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 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10086
  • No H1 headline

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

  • No XML sitemap

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

  • 36 internal links, 0 external

    The homepage links to 36 pages on saaspack.com and 0 external pages.

6 checks passed
  • Meta description: 130 characters

    Your meta description is 130 characters: “We are a Sales Force consulting Partner in CA Bay Area, Saaspack specialised in providing development and configuration…”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Salesforce Consulting Partner | Implementation | Saaspack”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: ImageObject, Organization, 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.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing url, logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://saaspack.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 (628 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix41
  • 1 linked page is broken

    Your homepage links to https://saaspack.com/industry, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages without a title

    https://saaspack.com/about and https://saaspack.com/contact have no <title>, so Google invents the link text in results.

  • 2 pages without a meta description

    https://saaspack.com/about and https://saaspack.com/contact have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://saaspack.com/about and https://saaspack.com/contact have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://saaspack.com/about and https://saaspack.com/contact took over 3 s to send their HTML from our server.

  • 3 internal pages checked

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

2 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

3 to fixGoogle 9285
  • 3 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 759 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact” and “Subscribe”.

  • 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: 4 testimonial or review blocks and 12 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

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.

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

  • 10 other companies contacted

    Loading the homepage contacts 10 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 saaspack.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 © 2023.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
GoDaddy

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on saaspack.com, including 10 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