Website review, no card needed

franciscansolutions.com logo

franciscansolutions.com website review

Visit site (opens in a new tab)Reviewed 30 October 202651 issues · 97 checks

This review found 51 issues worth fixing on franciscansolutions.com, 16 of them high impact, across 97 checks. The most urgent: page weight: 15.1 MB in 174 requests. 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
14.8 s1.6 sMay 9Oct 244.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.1 s
May 16, 20263.5 s
May 23, 20263.8 s
May 30, 20269.6 s
Jun 6, 202612.5 s
Jun 13, 202612.8 s
Jun 20, 202613.2 s
Jun 27, 202613.2 s
Jul 4, 202610.6 s
Jul 11, 20267.5 s
Jul 18, 20267.5 s
Jul 25, 20268.5 s
Aug 1, 20268.4 s
Aug 8, 202610.9 s
Aug 15, 202611.9 s
Aug 22, 202612.5 s
Aug 29, 202611.9 s
Sep 5, 202612.0 s
Sep 12, 202611.0 s
Sep 19, 202610.6 s
Sep 26, 202611.3 s
Oct 3, 20267.3 s
Oct 10, 20266.8 s
Oct 17, 20266.2 s
Oct 24, 20264.8 s
Real-visitor tap response (INP)75th percentile, phones
207 ms121 msMay 9Oct 24169 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026131 ms
May 16, 2026144 ms
May 23, 2026142 ms
May 30, 2026133 ms
Jun 6, 2026150 ms
Jun 13, 2026148 ms
Jun 20, 2026153 ms
Jun 27, 2026161 ms
Jul 4, 2026139 ms
Jul 11, 2026138 ms
Jul 18, 2026147 ms
Jul 25, 2026157 ms
Aug 1, 2026184 ms
Aug 8, 2026197 ms
Aug 15, 2026180 ms
Aug 22, 2026180 ms
Aug 29, 2026163 ms
Sep 5, 2026136 ms
Sep 12, 2026133 ms
Sep 19, 2026149 ms
Sep 26, 2026153 ms
Oct 3, 2026178 ms
Oct 10, 2026182 ms
Oct 17, 2026197 ms
Oct 24, 2026169 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 franciscansolutions.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. franciscansolutions.com at 0.5 s0.5 s
  2. franciscansolutions.com at 0.9 s0.9 s
  3. franciscansolutions.com at 1.4 s1.4 s
  4. franciscansolutions.com at 1.8 s1.8 s
  5. franciscansolutions.com at 2.3 s2.3 s
  6. franciscansolutions.com at 2.7 s2.7 s
  7. franciscansolutions.com at 3.2 s3.2 s
  8. franciscansolutions.com at 3.6 s3.6 s

Speed

8 to fix74
  • Render-blocking requests

    1.4 s

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

  • Main-thread work: 4.3 s

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

  • Improve image delivery

    1.6 MB

    23 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

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

  • Mobile performance score: 74

    74/100

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

  • Reduce unused JavaScript

    838 KiB

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

  • Google CDN adds 600 ms

    600 ms

    Google CDN costs a phone 600 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.

  • Google Tag Manager adds 354 ms

    354 ms

    Google Tag Manager costs a phone 354 ms of main-thread work and 505 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 166 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    30 KiB

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

  • Use efficient cache lifetimes

    15 KiB

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

  • Minify JavaScript

    11 KiB

    11 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    10 KiB

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

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 231 ms

    231 ms

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

Core Web Vitals

13 to fix33
  • 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.

  • Time to Interactive: 17.7 s

    17.7 s

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

  • Total Blocking Time: 667 ms

    667 ms

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user CLS: 0.14

    0.14

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

  • Tap response (INP) got 33% slower for real visitors

    +33%

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

  • Largest content (LCP) got 66% slower for real visitors

    +66%

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • 74 images without width and height

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

  • Speed Index: 4.3 s

    4.3 s

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

  • Largest Contentful Paint: 3.0 s

    3.0 s

    Your largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ONE SINGLE PLATFORM FOR YOUR SCHOOL”. Most of its time is element render delay (1.3 s).

  • First Contentful Paint: 1.8 s

    1.8 s

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

2 checks passed
  • Real-user INP: 129 ms

    129 ms

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

  • Cumulative Layout Shift: 0.008

    0.008

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

Images and page weight

3 to fix53
  • Page weight: 15.1 MB in 174 requests

    15.1 MB

    Your homepage downloads 15.1 MB in 174 requests on a phone: media 9.8 MB (1), images 2.9 MB (112) and scripts 1.7 MB (25). Under 2 MB keeps phones on slow connections fast.

  • 15 images in older formats

    15 images (962 KiB) 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.

  • 21 images below the first screen load straight away

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

  • About 4.3 g of CO₂ per visit

    4.29 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

16 to fixGoogle 6880
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • Hidden but focusable

    3 elements hidden from screen readers can still receive keyboard focus.

  • ARIA input fields must have an accessible name (3 elements)

    ARIA input fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • 5 links without text

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

  • 4 form fields without a label

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Alternative text of images should not be repeated as text (2 elements)

    Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

4 to fixGoogle 8584
  • Title is long (81 characters)

    Your title is 81 characters, so Google will cut it off around 60: “Best School ERP Software in India | Franciscan Solutions Trusted by 1000+ Schools”.

  • Meta description is long (178 characters)

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

  • 6 links crawlers can't follow

    6 links have no real href, so search engines can't follow them.

  • 3 links with vague text

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

  • 51 internal links, 9 external

    The homepage links to 51 pages on franciscansolutions.com and 9 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Franciscan e-Care”.

  • Canonical URL set

    The canonical URL is https://www.franciscansolutions.com/.

  • Structured data in place

    Structured data found: Organization.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.franciscansolutions.com/sitemap.xml.

AI search readiness

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

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.franciscansolutions.com/llms.txt (1 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix80
  • 1 page without a title

    https://www.franciscansolutions.com/blog.aspx has no <title>, so Google invents the link text in results.

  • 1 page without an H1

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

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

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

Best practices

2 to fixGoogle 9687
  • 8 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • 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 2,133 words of copy

    The homepage carries about 2,133 words of visible text.

6 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Sign Up with Facebook”, “Contact Us” and “Call Now”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 2 testimonial or review blocks, 20 customer or partner logos and “546170+ Students”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 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
  • 4 trackers load before any consent

    4

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

  • 7 cookies set on arrival

    7

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 franciscansolutions.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

Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 51 issues on franciscansolutions.com, including 21 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