Website review, no card needed

softlogic.lk logo

softlogic.lk website review

Visit site (opens in a new tab)Reviewed 27 October 202653 issues · 91 checks

This review found 53 issues worth fixing on softlogic.lk, 23 of them high impact, across 91 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 softlogic.lk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. softlogic.lk at 0.6 s0.6 s
  2. softlogic.lk at 1.1 s1.1 s
  3. softlogic.lk at 1.7 s1.7 s
  4. softlogic.lk at 2.3 s2.3 s
  5. softlogic.lk at 2.8 s2.8 s
  6. softlogic.lk at 3.4 s3.4 s
  7. softlogic.lk at 4.0 s4.0 s
  8. softlogic.lk at 4.6 s4.6 s

Speed

12 to fix23
  • Use efficient cache lifetimes

    15.8 s · 5.3 MB

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

  • Reduce unused JavaScript

    5.0 s · 934 KiB

    About 934 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.0 s faster on a phone.

  • Improve image delivery

    5.0 s · 917 KiB

    11 images could be 917 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.0 s faster on a phone.

  • Render-blocking requests

    3.3 s

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

  • Mobile performance score: 23

    23/100

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

  • 8 third-party services on the page

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

  • YouTube adds 911 ms

    911 ms

    YouTube costs a phone 911 ms of main-thread work and 965 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.

  • Reduce unused CSS

    600 ms · 158 KiB

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

  • Font display

    650 ms

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

  • Main-thread work: 3.7 s

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

  • 14 long tasks on the main thread

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

  • Google CDN adds 219 ms

    219 ms

    Google CDN costs a phone 219 ms of main-thread work and 348 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.

  • Document request latency

    27 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 70 but mobile only 23. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Minify JavaScript

    9 KiB

    9 KiB could be saved by minifying JavaScript.

  • 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
  • Server response: 183 ms

    183 ms

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

Core Web Vitals

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

  • Real-user LCP: 5.1 s

    5.1 s

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

  • Real-user CLS: 0.37

    0.37

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

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

  • Largest Contentful Paint: 31.8 s

    31.8 s

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

  • Time to Interactive: 35.3 s

    35.3 s

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

  • Speed Index: 8.5 s

    8.5 s

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Cumulative Layout Shift: 0.344

    0.344

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

  • Total Blocking Time: 832 ms

    832 ms

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • 13 images without width and height

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

1 checks passed
  • Real-user INP: 131 ms

    131 ms

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

Images and page weight

4 to fix35
  • Page weight: 7.0 MB in 73 requests

    7.0 MB

    Your homepage downloads 7.0 MB in 73 requests on a phone: images 4.8 MB (28), scripts 1.7 MB (21) and fonts 216 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 3.2 MB together. On a phone connection a single image that size takes seconds.

  • 19 images in older formats

    19 images (4.7 MB) 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.

  • 1 image far larger than shown

    26 KiB

    1 image is downloaded at several times the size a phone draws it, for example 220621110617m_slider01.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 26 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (208 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.0 g of CO₂ per visit

    1.98 g

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

Accessibility

8 to fixGoogle 6985
  • 3 buttons without a name

    3 buttons have no accessible name, so screen readers announce just “button”.

  • 7 text elements with low contrast

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 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 (12 elements)

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

  • 8 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 32 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 8 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 9268
  • Title is short (22 characters)

    Your title is only 22 characters: “Softlogic Holdings PLC”. 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.

  • 8 H1 headlines

    There are 8 <h1> headlines (“Healthcare”, “Retail” and “Financial”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (299 characters)

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

  • No social preview image

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

  • No robots.txt

    There is no robots.txt at softlogic.lk/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 39 internal links, 7 external

    The homepage links to 39 pages on softlogic.lk and 7 external pages.

1 checks passed
  • XML sitemap found

    Your XML sitemap is reachable at https://www.softlogic.lk/sitemap.xml.

AI search readiness

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

1 checks passed
  • Text is in the HTML

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

Other pages

1 to fix98
  • 15 pages share a meta description

    https://www.softlogic.lk/our-history, https://www.softlogic.lk/vision-mission, https://www.softlogic.lk/board-of-director, https://www.softlogic.lk/our-companies, https://www.softlogic.lk/corporate-information and https://www.softlogic.lk/financial-report and 9 others use the same meta description. A description written for each page earns more clicks.

  • 4 pages slow to respond

    https://www.softlogic.lk/our-history, https://www.softlogic.lk/vision-mission, https://www.softlogic.lk/board-of-director and https://www.softlogic.lk/our-companies took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

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

Best practices

2 to fixGoogle 7391
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 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 (Not Found)”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix56
  • 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.

  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

    The homepage carries about 267 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact” and “Contact Info”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

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

  • 6 cookies set on arrival

    6

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

  • 12 other companies contacted

    Loading the homepage contacts 12 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 softlogic.lk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics
Hosting
Oracle Cloud

Company

Founded
1991

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 53 issues on softlogic.lk, including 24 speed issues, 7 SEO issues and 5 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