Website review, no card needed

nupco.com logo

nupco.com website review

Visit site (opens in a new tab)Reviewed 1 November 202643 issues · 88 checks

This review found 43 issues worth fixing on nupco.com, 20 of them high impact, across 88 checks. The most urgent: improve image delivery. 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.3 s1.5 sMay 9Oct 244.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.9 s
May 16, 20261.9 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.8 s
Jul 18, 20262.3 s
Jul 25, 20263.1 s
Aug 1, 20263.5 s
Aug 8, 20263.5 s
Aug 15, 20263.4 s
Aug 22, 20263.5 s
Aug 29, 20263.4 s
Sep 5, 20263.3 s
Sep 12, 20263.0 s
Sep 19, 20262.7 s
Sep 26, 20262.5 s
Oct 3, 20262.8 s
Oct 10, 20263.3 s
Oct 17, 20263.7 s
Oct 24, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
312 ms98 msMay 9Oct 24144 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026287 ms
May 16, 2026287 ms
May 23, 2026287 ms
May 30, 2026287 ms
Jun 6, 2026281 ms
Jun 13, 2026280 ms
Jun 20, 2026284 ms
Jun 27, 2026286 ms
Jul 18, 2026256 ms
Jul 25, 2026185 ms
Aug 1, 2026123 ms
Aug 8, 2026133 ms
Aug 15, 2026137 ms
Aug 22, 2026140 ms
Aug 29, 2026139 ms
Sep 5, 2026131 ms
Sep 12, 2026136 ms
Sep 19, 2026154 ms
Sep 26, 2026158 ms
Oct 3, 2026161 ms
Oct 10, 2026159 ms
Oct 17, 2026141 ms
Oct 24, 2026144 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 nupco.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nupco.com at 1.6 s1.6 s
  2. nupco.com at 3.3 s3.3 s
  3. nupco.com at 4.9 s4.9 s
  4. nupco.com at 6.6 s6.6 s
  5. nupco.com at 8.2 s8.2 s
  6. nupco.com at 9.9 s9.9 s
  7. nupco.com at 11.5 s11.5 s
  8. nupco.com at 13.2 s13.2 s

Speed

12 to fix51
  • Improve image delivery

    5.5 s · 4.6 MB

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

  • Render-blocking requests

    4.9 s

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

  • Reduce unused JavaScript

    2.9 s · 1.5 MB

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

  • Font display

    3.0 s

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

  • Main-thread work: 7.2 s

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

  • 8 third-party services on the page

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

  • Mobile performance score: 51

    51/100

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

  • Google CDN adds 562 ms

    562 ms

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

  • YouTube adds 397 ms

    397 ms

    YouTube costs a phone 397 ms of main-thread work and 1,004 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

    300 ms · 164 KiB

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

  • Google Tag Manager adds 230 ms

    230 ms

    Google Tag Manager costs a phone 230 ms of main-thread work and 312 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.

  • 2,058 HTML elements

    The page has 2,058 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 15 long tasks on the main thread

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

  • Use efficient cache lifetimes

    59 KiB

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

  • Minify JavaScript

    14 KiB

    14 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    10 KiB

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

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

1 checks passed
  • Server response: 353 ms

    353 ms

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

Core Web Vitals

10 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: 5.5 s

    5.5 s

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

  • Real-user FCP: 4.4 s

    4.4 s

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

  • Real-user TTFB: 2.9 s

    2.9 s

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

  • Largest Contentful Paint: 18.4 s

    18.4 s

    Your largest element takes 18.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “حيث يلتقي الابتكار بالإمداد الصحي في نوبكو، نعيد تعريف مفهو…”. Most of its time is resource load delay (7.7 s).

  • Speed Index: 28.2 s

    28.2 s

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

  • Time to Interactive: 46.8 s

    46.8 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

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

    +105%

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

  • Total Blocking Time: 343 ms

    343 ms

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

4 checks passed
  • Real-user INP: 180 ms

    180 ms

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

  • Real-user CLS: 0.07

    0.07

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

  • Tap response (INP) got 50% faster for real visitors

    -50%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix35
  • Page weight: 25.5 MB in 189 requests

    25.5 MB

    Your homepage downloads 25.5 MB in 189 requests on a phone: images 21.1 MB (50), scripts 2.5 MB (52) and fonts 780 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

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

  • 18 images in older formats

    18 images (7.6 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

    62 KiB

    1 image is downloaded at several times the size a phone draws it, for example Floating-Image.png at 555 px wide, shown at 32 px. Resized copies would save about 62 KiB.

  • About 7.2 g of CO₂ per visit

    7.23 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 9295
  • 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.

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

  • 7 links without text

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 54 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

3 to fixGoogle 9278
  • No meta description

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

  • Title is short (16 characters)

    Your title is only 16 characters: “الرئيسية - nupco”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“بالإمداد الصحي” and “بالإمداد الصحي”). One clear main headline is easier for people and search engines.

  • 190 internal links, 24 external

    The homepage links to 190 pages on nupco.com and 24 external pages.

5 checks passed
  • Canonical URL set

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

  • 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.nupco.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.nupco.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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

Other pages

2 to fix90
  • 15 pages without a meta description

    https://www.nupco.com/about-nupco/%d9%84%d9%85%d8%ad%d8%a9-%d8%b9%d8%a7%d9%85%d8%a9, https://www.nupco.com/about-nupco/members, https://www.nupco.com/about-nupco/awards-and-achievements, https://www.nupco.com/about-nupco/social-responsibility, https://www.nupco.com/services-and-products/services-and-%d9%8ebusiness-solutions and https://www.nupco.com/services-and-products/our-products and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.nupco.com/about-nupco/%d9%84%d9%85%d8%ad%d8%a9-%d8%b9%d8%a7%d9%85%d8%a9, https://www.nupco.com/about-nupco/members, https://www.nupco.com/about-nupco/awards-and-achievements, https://www.nupco.com/about-nupco/social-responsibility, https://www.nupco.com/services-and-products/services-and-%d9%8ebusiness-solutions and https://www.nupco.com/services-and-products/our-products and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 pages with very little text

    https://www.nupco.com/about-nupco/%d9%84%d9%85%d8%ad%d8%a9-%d8%b9%d8%a7%d9%85%d8%a9, https://www.nupco.com/about-nupco/members, https://www.nupco.com/about-nupco/awards-and-achievements, https://www.nupco.com/about-nupco/social-responsibility, https://www.nupco.com/services-and-products/services-and-%d9%8ebusiness-solutions and https://www.nupco.com/services-and-products/our-products and 8 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.

  • 2 pages slow to respond

    https://www.nupco.com/about-nupco/social-responsibility and https://www.nupco.com/%d8%a7%d9%84%d9%85%d9%86%d8%a7%d9%81%d8%b3%d8%a7%d8%aa/tenders-list took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

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

  • 4 small tap targets

    4 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Browser-reported issues

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

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

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

  • 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 map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Only about 23 words

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

  • No opening hours

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

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

4 checks passed
  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

  • Phone number on the homepage

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

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 nupco.com, 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
Analytics
Google Analytics | Google Tag Manager
Hosting
Hwclouds As Ap Huawei Clouds

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on nupco.com, including 22 speed issues, 3 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