Website review, no card needed

liwastores.com logo

liwastores.com website review

Visit site (opens in a new tab)Reviewed 28 October 202633 issues · 74 checks

This review found 33 issues worth fixing on liwastores.com, 18 of them high impact, across 74 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
6.8 s4.0 sMay 9Oct 244.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.9 s
May 16, 20265.2 s
May 23, 20266.0 s
May 30, 20266.4 s
Jun 6, 20266.5 s
Jun 13, 20266.3 s
Jun 20, 20266.1 s
Jun 27, 20266.2 s
Jul 4, 20266.0 s
Jul 11, 20265.7 s
Jul 18, 20265.0 s
Jul 25, 20264.5 s
Aug 1, 20264.3 s
Aug 8, 20264.6 s
Aug 15, 20264.6 s
Aug 22, 20264.7 s
Aug 29, 20265.2 s
Sep 5, 20264.8 s
Sep 12, 20264.7 s
Sep 19, 20264.6 s
Sep 26, 20264.6 s
Oct 3, 20264.6 s
Oct 10, 20264.5 s
Oct 17, 20264.6 s
Oct 24, 20264.7 s
Real-visitor tap response (INP)75th percentile, phones
103 ms83 msMay 9Oct 24100 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202687 ms
May 16, 202689 ms
May 23, 2026101 ms
May 30, 2026101 ms
Jun 6, 2026101 ms
Jun 13, 202695 ms
Jun 20, 202688 ms
Jun 27, 202689 ms
Jul 4, 202685 ms
Jul 11, 202693 ms
Jul 18, 202694 ms
Jul 25, 202687 ms
Aug 1, 202687 ms
Aug 8, 202688 ms
Aug 15, 202687 ms
Aug 22, 202688 ms
Aug 29, 202687 ms
Sep 5, 202686 ms
Sep 12, 202686 ms
Sep 19, 202685 ms
Sep 26, 202686 ms
Oct 3, 202688 ms
Oct 10, 202689 ms
Oct 17, 202697 ms
Oct 24, 2026100 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 liwastores.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. liwastores.com at 1.9 s1.9 s
  2. liwastores.com at 3.9 s3.9 s
  3. liwastores.com at 5.8 s5.8 s
  4. liwastores.com at 7.8 s7.8 s
  5. liwastores.com at 9.7 s9.7 s
  6. liwastores.com at 11.6 s11.6 s
  7. liwastores.com at 13.6 s13.6 s
  8. liwastores.com at 15.5 s15.5 s

Speed

8 to fix51
  • Use efficient cache lifetimes

    8.1 s · 4.9 MB

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

  • Render-blocking requests

    11.8 s

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

  • Improve image delivery

    1.7 s · 2.9 MB

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

  • Reduce unused JavaScript

    1.9 s · 370 KiB

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

  • Reduce unused CSS

    1.4 s · 234 KiB

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

  • Mobile performance score: 51

    51/100

    Your mobile performance score is 51 (desktop: 63). Pages that score under 90 lose visitors before the first paint.

  • Main-thread work: 2.7 s

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

  • Google Maps adds 124 ms

    124 ms

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

  • 3 long tasks on the main thread

    3 long tasks block the main thread while loading, the longest for 219 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 Maps and Google Fonts), adding 548 KiB and 124 ms of main-thread time.

  • Minify CSS

    12 KiB

    12 KiB could be saved by minifying CSS.

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

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 6 ms

    6 ms

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

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 LCP: 5.3 s

    5.3 s

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

  • Real-user FCP: 5.1 s

    5.1 s

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

  • Real-user TTFB: 3.2 s

    3.2 s

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

  • Largest Contentful Paint: 13.4 s

    13.4 s

    Your largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (11.3 s).

  • Speed Index: 21.6 s

    21.6 s

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

  • First Contentful Paint: 7.4 s

    7.4 s

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

  • Time to Interactive: 17.3 s

    17.3 s

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

  • Real-user CLS: 0.13

    0.13

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

  • 18 images without width and height

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

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

    +12%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

2 checks passed
  • Total Blocking Time: 187 ms

    187 ms

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

  • Cumulative Layout Shift: 0.087

    0.087

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

Images and page weight

1 to fix33
  • Page weight: 5.1 MB in 168 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 168 requests on a phone: images 3.3 MB (49), scripts 834 KiB (43) and fonts 590 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • About 1.5 g of CO₂ per visit

    1.46 g

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

Accessibility

2 to fix84
  • 21 images without alt text

    21 images have no alt text, which hurts accessibility and image search.

  • 17 text elements with low contrast

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Headings skip levels

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

SEO

5 to fixGoogle 7766
  • No meta description

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

  • No H1 headline

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

  • Title is short (24 characters)

    Your title is only 24 characters: “Liwa Trading Enterprises”. 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.

  • 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 X (Twitter) card tag

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

  • 24 internal links, 63 external

    The homepage links to 24 pages on liwastores.com and 63 external pages.

3 checks passed
  • Canonical URL set

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

  • 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.liwastores.com/wp-sitemap.xml.

AI search readiness

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

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
  • 1 page without a meta description

    https://www.liwastores.com/bhs has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

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

  • 1 page with very little text

    https://www.liwastores.com/bhs has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 1 page slow to respond

    https://www.liwastores.com/bhs took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    1 page 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 1 page that loaded have a <title>.

Best practices

Google 100100
2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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 map 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 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 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 442 words of copy

    The homepage carries about 442 words of visible text.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact Us”.

  • Social proof on the page

    Social proof on the homepage: 14 customer or partner logos, 3 trust badges and “0 M HAPPY CUSTOMERS”.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

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

Upkeep, stack and company

Stack

Hosting
GoDaddy

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on liwastores.com, including 18 speed issues, 5 SEO issues and 4 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