Website review, no card needed

ghaddar.com logo

ghaddar.com website review

Visit site (opens in a new tab)Reviewed 18 October 202636 issues · 87 checks

This review found 36 issues worth fixing on ghaddar.com, 15 of them high impact, across 87 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.0 s3.5 sApr 25Oct 105.7 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20264.4 s
May 2, 20264.4 s
May 9, 20264.4 s
May 16, 20264.3 s
May 23, 20264.4 s
May 30, 20264.5 s
Jun 6, 20264.6 s
Jun 13, 20264.8 s
Jun 20, 20265.0 s
Jun 27, 20264.8 s
Jul 4, 20264.7 s
Jul 11, 20264.7 s
Jul 18, 20264.7 s
Jul 25, 20264.5 s
Aug 1, 20264.6 s
Aug 8, 20264.8 s
Aug 15, 20264.7 s
Aug 22, 20265.5 s
Aug 29, 20265.4 s
Sep 5, 20263.8 s
Sep 12, 20263.8 s
Sep 19, 20263.9 s
Sep 26, 20263.9 s
Oct 3, 20265.3 s
Oct 10, 20265.7 s
Real-visitor tap response (INP)75th percentile, phones
180 ms83 msApr 25Oct 10122 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026119 ms
May 2, 2026116 ms
May 9, 202699 ms
May 16, 202694 ms
May 23, 2026111 ms
May 30, 2026109 ms
Jun 6, 2026114 ms
Jun 27, 2026137 ms
Jul 11, 2026142 ms
Jul 18, 2026136 ms
Jul 25, 2026132 ms
Aug 1, 2026126 ms
Aug 8, 2026115 ms
Aug 15, 2026106 ms
Aug 22, 2026113 ms
Aug 29, 2026127 ms
Sep 5, 2026167 ms
Sep 12, 2026169 ms
Sep 19, 2026169 ms
Sep 26, 2026161 ms
Oct 3, 2026125 ms
Oct 10, 2026122 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 ghaddar.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ghaddar.com at 1.4 s1.4 s
  2. ghaddar.com at 2.8 s2.8 s
  3. ghaddar.com at 4.1 s4.1 s
  4. ghaddar.com at 5.5 s5.5 s
  5. ghaddar.com at 6.9 s6.9 s
  6. ghaddar.com at 8.3 s8.3 s
  7. ghaddar.com at 9.7 s9.7 s
  8. ghaddar.com at 11.1 s11.1 s

Speed

8 to fix55
  • Use efficient cache lifetimes

    1.9 s · 2.2 MB

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

  • Improve image delivery

    1.4 s · 908 KiB

    20 images could be 908 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

  • Render-blocking requests

    1.8 s

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

  • Mobile performance score: 55

    55/100

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

  • Main-thread work: 3.8 s

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

  • Reduce unused CSS

    300 ms · 70 KiB

    About 70 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

    276 KiB

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

  • 1,621 HTML elements

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Cloudflare and Google Fonts and others), adding 312 KiB and 220 ms of main-thread time.

  • Font display

    200 ms

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

  • 20 long tasks on the main thread

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

  • Minify JavaScript

    23 KiB

    23 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: 106 ms

    106 ms

    Your server sent the HTML in 106 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: 5.6 s

    5.6 s

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

  • Real-user FCP: 4.9 s

    4.9 s

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

  • Real-user TTFB: 3.6 s

    3.6 s

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

  • Speed Index: 16.7 s

    16.7 s

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

  • Time to Interactive: 16.0 s

    16.0 s

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

  • Largest Contentful Paint: 5.4 s

    5.4 s

    Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Ghaddar Machinery Co.”. Most of its time is resource load delay (3.7 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 25% slower for real visitors

    +25%

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

  • Total Blocking Time: 378 ms

    378 ms

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

  • 23 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +5%

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

3 checks passed
  • Real-user INP: 131 ms

    131 ms

    Real visitors wait 131 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.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix75
  • Page weight: 3.6 MB in 151 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 151 requests on a phone: images 2.3 MB (32), scripts 898 KiB (62) and fonts 248 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 15 images in older formats

    15 images (1.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.

  • About 1.0 g of CO₂ per visit

    1.03 g

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

2 checks passed
  • Images load when needed

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

  • 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 8990
  • 7 buttons without a name

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

  • 10 text elements with low contrast

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

  • 9 images without alt text

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

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

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 26 links without text

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

  • 2 form fields without a label

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 6 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 8586
  • No H1 headline

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

  • 19 links with vague text

    19 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 4 links crawlers can't follow

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

  • 156 internal links, 5 external

    The homepage links to 156 pages on ghaddar.com and 5 external pages.

7 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Ghaddar Machinery: Leading OEM for Kubota, John Deere & Cummins industrial generators. High-quality power solutions for…”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Industrial Generators Lebanon & Africa | Ghaddar Machinery”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, 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://ghaddar.com/news-sitemap.xml.

AI search readiness

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (780 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://ghaddar.com/llms.txt (184 KiB, 1,139 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 4 pages without a meta description

    https://ghaddar.com/fr, https://ghaddar.com/contact-us, https://ghaddar.com/news and https://ghaddar.com/faq have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://ghaddar.com/fr, https://ghaddar.com/contact-us, https://ghaddar.com/news, https://ghaddar.com/faq, https://ghaddar.com/about-us-2 and https://ghaddar.com/products and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://ghaddar.com/fr took over 3 s to send its 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

1 to fixGoogle 7393
  • 44 small tap targets

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

  • 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 (“Mixed content”).

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

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

    The homepage carries about 657 words of visible text.

6 checks passed
  • Clear next step on the first screen

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

  • 1 call to action

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

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 5 testimonial or review blocks, 6 customer or partner logos and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 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.

  • 8 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on ghaddar.com, including 19 speed issues and 3 SEO issues. 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