Website review, no card needed

aralgosaibico.com logo

aralgosaibico.com website review

Visit site (opens in a new tab)Reviewed 17 November 202634 issues · 86 checks

This review found 34 issues worth fixing on aralgosaibico.com, 13 of them high impact, across 86 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
9.2 s3.3 sMay 30Nov 144.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20266.6 s
Jun 6, 20266.3 s
Jun 13, 20266.4 s
Jun 20, 20266.5 s
Jun 27, 20266.3 s
Jul 4, 20265.9 s
Jul 11, 20265.6 s
Jul 18, 20265.7 s
Jul 25, 20265.7 s
Aug 1, 20265.5 s
Aug 8, 20265.5 s
Aug 15, 20265.6 s
Aug 22, 20266.1 s
Aug 29, 20266.7 s
Sep 5, 20267.5 s
Sep 12, 20267.9 s
Sep 19, 20268.3 s
Sep 26, 20268.4 s
Oct 3, 20268.1 s
Oct 10, 20268.1 s
Oct 17, 20268.5 s
Oct 24, 20268.3 s
Oct 31, 20267.4 s
Nov 7, 20266.0 s
Nov 14, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
120 ms96 msMay 30Nov 14105 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026105 ms
Jun 6, 2026111 ms
Jun 13, 2026111 ms
Jun 20, 2026113 ms
Jun 27, 2026112 ms
Jul 4, 2026110 ms
Jul 11, 2026106 ms
Jul 18, 2026106 ms
Jul 25, 2026104 ms
Aug 1, 2026113 ms
Aug 8, 2026112 ms
Aug 15, 2026115 ms
Aug 22, 2026117 ms
Aug 29, 2026110 ms
Sep 5, 2026111 ms
Sep 12, 2026107 ms
Sep 19, 2026100 ms
Sep 26, 2026102 ms
Oct 3, 2026101 ms
Oct 10, 202699 ms
Oct 17, 2026106 ms
Oct 24, 2026106 ms
Oct 31, 2026116 ms
Nov 7, 2026105 ms
Nov 14, 2026105 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 aralgosaibico.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aralgosaibico.com at 0.7 s0.7 s
  2. aralgosaibico.com at 1.3 s1.3 s
  3. aralgosaibico.com at 2.0 s2.0 s
  4. aralgosaibico.com at 2.7 s2.7 s
  5. aralgosaibico.com at 3.3 s3.3 s
  6. aralgosaibico.com at 4.0 s4.0 s
  7. aralgosaibico.com at 4.7 s4.7 s
  8. aralgosaibico.com at 5.3 s5.3 s

Speed

8 to fix77
  • Use efficient cache lifetimes

    3.4 s · 3.6 MB

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

  • Render-blocking requests

    1.8 s

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

  • Improve image delivery

    500 ms · 1.9 MB

    13 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • Mobile performance score: 77

    77/100

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

  • Font display

    450 ms

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

  • Reduce unused CSS

    300 ms · 93 KiB

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

  • Reduce unused JavaScript

    372 KiB

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

  • Google CDN adds 254 ms

    254 ms

    Google CDN costs a phone 254 ms of main-thread work and 742 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 third-party services on the page

    3 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Fonts), adding 838 KiB and 288 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Legacy JavaScript

    22 KiB

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

  • Minify CSS

    9 KiB

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

2 checks passed
  • Main-thread work: 1.6 s

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

  • Server response: 25 ms

    25 ms

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

Core Web Vitals

8 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: 4.5 s

    4.5 s

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

  • Real-user FCP: 4.7 s

    4.7 s

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

  • Real-user TTFB: 4.8 s

    4.8 s

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

  • Time to Interactive: 12.6 s

    12.6 s

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

  • Largest Contentful Paint: 5.0 s

    5.0 s

    Your largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Medical and scientific equipment”.

  • Speed Index: 5.1 s

    5.1 s

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -3%

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

6 checks passed
  • Real-user INP: 103 ms

    103 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Largest content (LCP) got 22% faster for real visitors

    -22%

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 34 ms

    34 ms

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

Images and page weight

5 to fix25
  • Page weight: 4.8 MB in 77 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 77 requests on a phone: images 2.9 MB (32), scripts 813 KiB (16) and fonts 559 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Mask-Group-11.png.webp weighs 549 KiB. On a phone connection a single image that size takes seconds.

  • 9 images in older formats

    9 images (1.3 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.

  • An image on the first screen is lazy-loaded

    VET-silder.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image far larger than shown

    42 KiB

    1 image is downloaded at several times the size a phone draws it, for example Mask-Group-11.png.webp at 1,061 px wide, shown at 340 px. Resized copies would save about 42 KiB.

  • About 1.4 g of CO₂ per visit

    1.35 g

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

Accessibility

4 to fixGoogle 9495
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

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

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

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

2 checks passed
  • Every image has alt text

    All 56 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 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 8598
  • 3 links crawlers can't follow

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

  • 107 internal links, 11 external

    The homepage links to 107 pages on aralgosaibico.com and 11 external pages.

8 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Abdulrehman Algosaibi G.T.C. supplies pharmaceuticals, medical devices and healthcare logistics in Saudi Arabia, with c…”.

  • One H1 headline

    Your main headline reads: “شركة عبدالرحمن القصيبي للتجارة العامة”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “شركة عبدالرحمن القصيبي | توزيع الأدوية والأجهزة الطبية”.

  • Canonical URL set

    The canonical URL is https://aralgosaibico.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, CollectionPage, LocalBusiness, Organization 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://aralgosaibico.com/sitemap.xml.

AI search readiness

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

  • llms.txt published

    The site publishes https://aralgosaibico.com/llms.txt (80 KiB, 255 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 15 links to non-canonical URLs

    Your homepage links to 15 pages by a URL that isn't their canonical one, for example https://aralgosaibico.com/who-we-are, whose canonical is https://aralgosaibico.com/who-we-are?lang=ar. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 pages with very little text

    https://aralgosaibico.com/who-we-are, https://aralgosaibico.com/business-overview, https://aralgosaibico.com/divisional-activitie/medical-scientific, https://aralgosaibico.com/divisional-activitie/%d8%aa%d9%88%d8%b2%d9%8a%d8%b9-%d8%a7%d9%84%d8%a3%d8%af%d9%88%d9%8a%d8%a9, https://aralgosaibico.com/divisional-activitie/dental-operations and https://aralgosaibico.com/divisional-activitie/veterinary and 9 others have 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.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 1 low-resolution image

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix65
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • Only about 19 words

    The homepage has only about 19 words of visible text; thin pages give Google and first-time buyers little to go on.

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

5 checks passed
  • 1 short form

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

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 1 cookie set on arrival

    1

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 aralgosaibico.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 © 2013.

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics
Hosting
Hetzner

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 aralgosaibico.com, including 16 speed issues, 1 SEO issue 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