Website review, no card needed

scileasecorp.ca logo

scileasecorp.ca website review

Visit site (opens in a new tab)Reviewed 18 October 202631 issues · 70 checks

This review found 31 issues worth fixing on scileasecorp.ca, 14 of them high impact, across 70 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
4.7 s3.8 sAug 29Oct 33.9 s
Show as table
DateReal-visitor load time (LCP)
Aug 29, 20264.6 s
Sep 5, 20264.0 s
Sep 12, 20264.3 s
Sep 19, 20264.0 s
Sep 26, 20263.9 s
Oct 3, 20263.9 s

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 scileasecorp.ca (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. scileasecorp.ca at 0.6 s0.6 s
  2. scileasecorp.ca at 1.3 s1.3 s
  3. scileasecorp.ca at 1.9 s1.9 s
  4. scileasecorp.ca at 2.5 s2.5 s
  5. scileasecorp.ca at 3.2 s3.2 s
  6. scileasecorp.ca at 3.8 s3.8 s
  7. scileasecorp.ca at 4.5 s4.5 s
  8. scileasecorp.ca at 5.1 s5.1 s

Speed

8 to fix36
  • Use efficient cache lifetimes

    8.8 s · 1.7 MB

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

  • Improve image delivery

    6.5 s · 1.2 MB

    2 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.5 s faster on a phone.

  • Render-blocking requests

    3.8 s

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

  • Mobile performance score: 36

    36/100

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

  • Document request latency

    900 ms

    The HTML itself could arrive about 900 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    886 ms

    Reduce initial server response time. Google estimates savings of 886 ms on a phone.

  • Minify JavaScript

    510 ms · 70 KiB

    70 KiB could be saved by minifying JavaScript.

  • Server response: 986 ms

    986 ms

    Your server takes 986 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Reduce unused CSS

    170 ms · 53 KiB

    About 53 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 170 ms faster on a phone.

  • Reduce unused JavaScript

    170 ms · 21 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (FontAwesome CDN, Cloudflare CDN and moneris.com and others), adding 321 KiB and 126 ms of main-thread time.

  • Font display

    150 ms

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

  • 3 long tasks on the main thread

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Main-thread work: 0.9 s

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

Core Web Vitals

10 to fix0
  • 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.

  • Real-user FCP: 3.8 s

    3.8 s

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

  • Real-user TTFB: 2.6 s

    2.6 s

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

  • Largest Contentful Paint: 13.5 s

    13.5 s

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

  • Cumulative Layout Shift: 0.613

    0.613

    The layout shifts by 0.613 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Time to Interactive: 13.5 s

    13.5 s

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

  • First Contentful Paint: 4.6 s

    4.6 s

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

  • Speed Index: 8.6 s

    8.6 s

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

  • Real-user LCP: 3.8 s

    3.8 s

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

  • Real-user CLS: 0.15

    0.15

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

2 checks passed
  • Largest content (LCP) got 10% faster for real visitors

    -10%

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

  • Total Blocking Time: 30 ms

    30 ms

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

Images and page weight

1 to fix50
  • Page weight: 2.1 MB in 74 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 74 requests on a phone: images 1.3 MB (10), fonts 369 KiB (6) and scripts 248 KiB (34). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.60 g

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

Accessibility

1 to fix98
  • 1 link without text

    1 link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

1 checks passed
  • Every image has alt text

    All 10 images in the HTML carry an alt attribute.

SEO

4 to fixGoogle 8576
  • No meta description

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

  • Title is short (21 characters)

    Your title is only 21 characters: “Home - SCI Lease Corp”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Home” and “Welcome to Lease Corp”). One clear main headline is easier for people and search engines.

  • 2 links crawlers can't follow

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

  • 64 internal links, 12 external

    The homepage links to 64 pages on scileasecorp.ca and 12 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.scileasecorp.ca/sitemap_index.xml.

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. 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://www.scileasecorp.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
  • 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.

Other pages

2 to fix90
  • 5 pages without a meta description

    https://www.scileasecorp.ca/make-a-payment, https://www.scileasecorp.ca/media/Lease-Maturity-Brochure-ROC_EN, https://www.scileasecorp.ca/media/VF-Lease-Maturity-Brochure-EN-ROC, https://www.scileasecorp.ca/media/Lease-Maturity-Brochure-QC_EN and https://www.scileasecorp.ca/media/VF-Lease-Maturity-Brochure-EN have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://www.scileasecorp.ca/media/Lease-Maturity-Brochure-ROC_EN, https://www.scileasecorp.ca/media/VF-Lease-Maturity-Brochure-EN-ROC, https://www.scileasecorp.ca/media/Lease-Maturity-Brochure-QC_EN and https://www.scileasecorp.ca/media/VF-Lease-Maturity-Brochure-EN have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.scileasecorp.ca/make-a-payment took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    5 pages of 15 loaded without an error (the rest turned automated requests away).

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

Best practices

1 to fixGoogle 9293
  • 2 console errors

    2 errors were logged to the browser console during Google's test (“Access to script at 'https://polyfill.io/v3/polyfill.min.js?flags=gated&features=default%2CString.p…”).

  • 1 low-resolution image

    1 image is 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

3 to fix67
  • No social proof

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

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 494 words of visible text.

3 checks passed
  • 3 calls to action

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

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 3 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

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 scileasecorp.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce

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 scileasecorp.ca, including 18 speed issues, 4 SEO issues and 3 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