Website review, no card needed

newyousa.com logo

newyousa.com website review

Visit site (opens in a new tab)Reviewed 19 October 202644 issues · 93 checks

This review found 44 issues worth fixing on newyousa.com, 13 of them high impact, across 93 checks. The most urgent: render-blocking requests. 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
3.6 s2.0 sApr 25Oct 102.6 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20263.4 s
May 2, 20263.4 s
May 9, 20263.3 s
May 16, 20263.2 s
May 23, 20262.9 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20263.0 s
Jun 20, 20263.1 s
Jun 27, 20263.2 s
Jul 4, 20263.2 s
Jul 11, 20263.2 s
Jul 18, 20263.1 s
Jul 25, 20263.1 s
Aug 1, 20263.1 s
Aug 8, 20263.1 s
Aug 15, 20263.1 s
Aug 22, 20263.0 s
Aug 29, 20262.9 s
Oct 3, 20262.2 s
Oct 10, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
404 ms112 msApr 25Oct 10146 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026256 ms
May 2, 2026261 ms
May 9, 2026250 ms
May 16, 2026229 ms
May 23, 2026246 ms
May 30, 2026248 ms
Jun 6, 2026237 ms
Jun 13, 2026256 ms
Jun 20, 2026259 ms
Jun 27, 2026268 ms
Jul 4, 2026298 ms
Jul 11, 2026331 ms
Jul 18, 2026350 ms
Jul 25, 2026359 ms
Aug 1, 2026370 ms
Aug 8, 2026343 ms
Aug 15, 2026335 ms
Aug 22, 2026323 ms
Aug 29, 2026249 ms
Oct 10, 2026146 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 newyousa.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. newyousa.com at 0.4 s0.4 s
  2. newyousa.com at 0.8 s0.8 s
  3. newyousa.com at 1.1 s1.1 s
  4. newyousa.com at 1.5 s1.5 s
  5. newyousa.com at 1.9 s1.9 s
  6. newyousa.com at 2.3 s2.3 s
  7. newyousa.com at 2.6 s2.6 s
  8. newyousa.com at 3.0 s3.0 s

Speed

9 to fix75
  • Render-blocking requests

    2.4 s

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

  • Use efficient cache lifetimes

    600 ms · 7.3 MB

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

  • Improve image delivery

    300 ms · 6.6 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, TikTok and Facebook and others), adding 1.7 MB and 1.0 s of main-thread time.

  • Mobile performance score: 75

    75/100

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

  • Reduce unused JavaScript

    940 KiB

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

  • Google Tag Manager adds 627 ms

    627 ms

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

  • Reduce unused CSS

    300 ms · 65 KiB

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

  • TikTok adds 211 ms

    211 ms

    TikTok costs a phone 211 ms of main-thread work and 296 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.

  • 9 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    42 KiB

    Polyfills for old browsers add 42 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.

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.8 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Time to Interactive: 19.0 s

    19.0 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Largest Contentful Paint: 4.1 s

    4.1 s

    Your largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “اكتشف أفضل نسخة منك مع رعاية جمالية وصحية متخصصة”.

  • Real-user TTFB: 890 ms

    890 ms

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

  • Speed Index: 3.6 s

    3.6 s

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

  • Total Blocking Time: 220 ms

    220 ms

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

  • 2 images without width and height

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

6 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.8 s

    1.8 s

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

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

    -24%

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

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

    -29%

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

  • Cumulative Layout Shift: 0.01

    0.01

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

Images and page weight

4 to fix38
  • Page weight: 9.6 MB in 104 requests

    9.6 MB

    Your homepage downloads 9.6 MB in 104 requests on a phone: images 7.4 MB (31), scripts 1.7 MB (28) and fonts 364 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 6.5 MB together. On a phone connection a single image that size takes seconds.

  • 18 images in older formats

    18 images (7.4 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.

  • 9 images below the first screen load straight away

    9 images further down the page (7.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.7 g of CO₂ per visit

    2.73 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 7788
  • 19 buttons without a name

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

  • Unlabelled dropdowns

    2 dropdowns have no label.

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

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

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

  • 32 links without text

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

  • 4 form fields without a label

    4 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 34 images in the HTML carry an alt attribute.

  • 36 automated accessibility rules passed

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

SEO

3 to fixGoogle 10084
  • Title is short (13 characters)

    Your title is only 13 characters: “عيادات نـيويو”. 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.

  • Meta description is long (185 characters)

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

  • 87 internal links, 44 external

    The homepage links to 87 pages on newyousa.com and 44 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “اكتشف أفضل نسخة منك مع رعاية جمالية وصحية متخصصة”.

  • Canonical URL set

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

  • 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://newyousa.com/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.newyousa.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

3 to fix81
  • 2 pages point its canonical at the homepage

    https://www.newyousa.com/lang/en and https://www.newyousa.com/lang/ar declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 3 pages share a title

    /, https://www.newyousa.com/lang/en and https://www.newyousa.com/lang/ar all use the title “عيادات نـيويو”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages share a meta description

    https://www.newyousa.com/lang/en, https://www.newyousa.com/lang/ar, https://www.newyousa.com/aboutUs, https://www.newyousa.com/services/3/%D8%A7%D9%84%D8%B3%D9%85%D9%86%D8%A9, https://www.newyousa.com/services/4/%D8%AA%D8%AC%D9%85%D9%8A%D9%84-%D8%AC%D8%B1%D8%A7%D8%AD%D9%8A and https://www.newyousa.com/services/9/%D8%AC%D9%84%D8%AF%D9%8A%D8%A9-%D9%88%D8%AA%D8%AC%D9%85%D9%8A%D9%84 and 9 others use the same meta description. A description written for each page earns more clicks.

  • 15 pages with very little text

    https://www.newyousa.com/lang/en, https://www.newyousa.com/lang/ar, https://www.newyousa.com/aboutUs, https://www.newyousa.com/services/3/%D8%A7%D9%84%D8%B3%D9%85%D9%86%D8%A9, https://www.newyousa.com/services/4/%D8%AA%D8%AC%D9%85%D9%8A%D9%84-%D8%AC%D8%B1%D8%A7%D8%AD%D9%8A and https://www.newyousa.com/services/9/%D8%AC%D9%84%D8%AF%D9%8A%D8%A9-%D9%88%D8%AA%D8%AC%D9%85%D9%8A%D9%84 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 28 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

4 to fixGoogle 6974
  • 1 broken image

    1 image failed to load on a phone, for example https://www.newyousa.com/media/logos/innovative-care.jpeg.

  • 10 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

  • 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

3 to fix78
  • 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.

  • 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 33 words

    The homepage has only about 33 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.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact us on WhatsApp”.

  • 1 short form

    A short form (4 fields at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 23 testimonial or review blocks and 3 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Snap Pixel and 1 more (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.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies (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.

  • 21 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on newyousa.com, including 17 speed issues, 3 SEO issues 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