Website review, no card needed

locuz.com logo

locuz.com website review

Visit site (opens in a new tab)Reviewed 2 November 202634 issues · 83 checks

This review found 34 issues worth fixing on locuz.com, 17 of them high impact, across 83 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
11.2 s5.3 sMay 16Oct 319.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20266.0 s
May 23, 20266.0 s
May 30, 20266.0 s
Jun 6, 20266.2 s
Jun 13, 20266.2 s
Jun 20, 20267.0 s
Jun 27, 20268.0 s
Jul 4, 20269.8 s
Jul 11, 202610.5 s
Jul 18, 20269.1 s
Jul 25, 20268.9 s
Aug 1, 20268.7 s
Aug 8, 20268.5 s
Aug 15, 20268.5 s
Aug 22, 20268.2 s
Aug 29, 20268.5 s
Sep 5, 20268.5 s
Sep 12, 20268.5 s
Sep 19, 20268.7 s
Sep 26, 20268.6 s
Oct 3, 20268.9 s
Oct 10, 20269.2 s
Oct 17, 20269.2 s
Oct 24, 20269.0 s
Oct 31, 20269.0 s
Real-visitor tap response (INP)75th percentile, phones
137 ms87 msMay 16Oct 31130 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026108 ms
May 23, 2026109 ms
May 30, 2026113 ms
Jun 6, 2026130 ms
Jun 13, 2026131 ms
Jun 20, 2026128 ms
Jun 27, 2026122 ms
Jul 4, 202697 ms
Jul 11, 202697 ms
Jul 18, 202695 ms
Jul 25, 202695 ms
Aug 1, 202696 ms
Aug 8, 202693 ms
Aug 15, 202699 ms
Aug 22, 202694 ms
Aug 29, 202695 ms
Sep 5, 202699 ms
Sep 12, 2026103 ms
Sep 19, 2026116 ms
Sep 26, 2026122 ms
Oct 3, 2026123 ms
Oct 10, 2026124 ms
Oct 17, 2026125 ms
Oct 24, 2026130 ms
Oct 31, 2026130 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 locuz.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. locuz.com at 1.1 s1.1 s
  2. locuz.com at 2.3 s2.3 s
  3. locuz.com at 3.4 s3.4 s
  4. locuz.com at 4.5 s4.5 s
  5. locuz.com at 5.6 s5.6 s
  6. locuz.com at 6.8 s6.8 s
  7. locuz.com at 7.9 s7.9 s
  8. locuz.com at 9.0 s9.0 s

Speed

8 to fix55
  • Use efficient cache lifetimes

    20.4 s · 19.4 MB

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

  • Render-blocking requests

    11.1 s

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

  • Reduce unused CSS

    8.1 s · 1.4 MB

    About 1.4 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 8.1 s faster on a phone.

  • Reduce unused JavaScript

    7.4 s · 1.3 MB

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

  • Minify JavaScript

    1.2 s · 204 KiB

    204 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 55

    55/100

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

  • Font display

    600 ms

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

  • Minify CSS

    450 ms · 72 KiB

    72 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    200 ms · 30 KiB

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

  • Improve image delivery

    183 KiB

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

  • Document request latency

    144 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 51 ms. During a long task the page ignores taps.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Fonts and sw-themes.com), adding 166 KiB and 2 ms of main-thread time.

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

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

  • Server response: 125 ms

    125 ms

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

Core Web Vitals

11 to fix67
  • 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: 10.1 s

    10.1 s

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

  • Real-user FCP: 9.5 s

    9.5 s

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

  • Real-user TTFB: 2.8 s

    2.8 s

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

  • First Contentful Paint: 12.9 s

    12.9 s

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

  • Largest Contentful Paint: 28.2 s

    28.2 s

    Your largest element takes 28.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Snowflake Partner of the Year”.

  • Speed Index: 20.3 s

    20.3 s

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

  • Time to Interactive: 29.8 s

    29.8 s

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

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

    +20%

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

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

    +50%

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

  • 31 images without width and height

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

4 checks passed
  • Real-user INP: 142 ms

    142 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Cumulative Layout Shift: 0.04

    0.04

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

  • Total Blocking Time: 1 ms

    1 ms

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

Images and page weight

3 to fix50
  • Page weight: 19.8 MB in 136 requests

    19.8 MB

    Your homepage downloads 19.8 MB in 136 requests on a phone: media 14.6 MB (2), scripts 2.1 MB (39) and stylesheets 1.6 MB (54). Under 2 MB keeps phones on slow connections fast.

  • 6 images in older formats

    6 images (540 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.

  • 1 image far larger than shown

    95 KiB

    1 image is downloaded at several times the size a phone draws it, for example SHI-Snowflake-Partner-of-the-Year.jpg at 1,536 px wide, shown at 378 px. Resized copies would save about 95 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (26 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 5.6 g of CO₂ per visit

    5.61 g

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

Accessibility

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

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

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

    All page content should be contained by landmarks: 38 elements on the page fail this check, rated moderate by axe-core.

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

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

2 checks passed
  • Every image has alt text

    All 38 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

1 to fixGoogle 10093
  • Title is long (72 characters)

    Your title is 72 characters, so Google will cut it off around 60: “Digital Transformation Services & Solutions - SHI India (Formerly Locuz)”.

  • 209 internal links, 14 external

    The homepage links to 209 pages on locuz.com and 14 external pages.

7 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “We offer digital transformation services & solutions, helping enterprises migrate to the cloud, enhance digital operati…”.

  • One H1 headline

    Your main headline reads: “Simplifying Digital Transformation for your Enterprise”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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.locuz.com/sitemap_index.xml.

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.locuz.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 (1,990 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 pages slow to respond

    https://www.locuz.com/data-analytics, https://www.locuz.com/locuz-enabling-renewable-energy-sector-to-make-data-driven-decisions, https://www.locuz.com/snowflake, https://www.locuz.com/aws-data-analytics, https://www.locuz.com/generative-ai and https://www.locuz.com/hybrid-cloud-management and 9 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 95 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 9687
  • 2 small tap targets

    2 of 10 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: net::ERR_FAILED”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix60
  • 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 analytics detected

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

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

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

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

    The homepage carries about 536 words of visible text.

  • Urgency cues

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

2 checks passed
  • 3 calls to action

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

  • Social proof on the page

    Social proof on the homepage: 71 testimonial or review blocks and 8 customer or partner logos.

Privacy and tracking

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

  • 3 other companies contacted

    Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 locuz.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 © 2022.

Stack

CMS
WordPress
Framework
jQuery
Hosting
Azure

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on locuz.com, including 19 speed issues, 1 SEO issue 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