Website review, no card needed

ormat.com logo

ormat.com website review

Visit site (opens in a new tab)Reviewed 27 October 202642 issues · 90 checks

This review found 42 issues worth fixing on ormat.com, 11 of them high impact, across 90 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
4.9 s2.5 sMay 9Oct 242.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.3 s
May 16, 20263.5 s
May 23, 20263.7 s
May 30, 20263.8 s
Jun 6, 20264.1 s
Jun 13, 20264.2 s
Jun 20, 20264.1 s
Jun 27, 20264.1 s
Jul 4, 20264.1 s
Jul 11, 20264.1 s
Jul 18, 20264.2 s
Jul 25, 20264.3 s
Aug 1, 20264.5 s
Aug 8, 20264.6 s
Aug 15, 20264.4 s
Aug 22, 20264.4 s
Aug 29, 20264.4 s
Sep 5, 20264.3 s
Sep 12, 20264.5 s
Sep 19, 20264.0 s
Sep 26, 20263.6 s
Oct 3, 20263.3 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Oct 24, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
100 ms76 msMay 9Oct 2479 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202689 ms
May 16, 202692 ms
May 23, 202691 ms
May 30, 202696 ms
Jun 6, 202697 ms
Jun 13, 202695 ms
Jun 20, 202695 ms
Jun 27, 202692 ms
Jul 4, 202691 ms
Jul 11, 202692 ms
Jul 18, 202692 ms
Jul 25, 202694 ms
Aug 1, 202693 ms
Aug 8, 202696 ms
Aug 15, 202695 ms
Aug 22, 202694 ms
Aug 29, 202695 ms
Sep 5, 202694 ms
Sep 12, 202695 ms
Sep 19, 202693 ms
Sep 26, 202687 ms
Oct 3, 202687 ms
Oct 10, 202682 ms
Oct 17, 202679 ms
Oct 24, 202679 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 ormat.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ormat.com at 0.6 s0.6 s
  2. ormat.com at 1.2 s1.2 s
  3. ormat.com at 1.8 s1.8 s
  4. ormat.com at 2.4 s2.4 s
  5. ormat.com at 3.0 s3.0 s
  6. ormat.com at 3.7 s3.7 s
  7. ormat.com at 4.3 s4.3 s
  8. ormat.com at 4.9 s4.9 s

Speed

10 to fix57
  • Use efficient cache lifetimes

    1.9 s · 3.5 MB

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

  • Render-blocking requests

    5.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Cachefly and Cloudflare CDN and others), adding 4.6 MB and 961 ms of main-thread time.

  • Improve image delivery

    1.4 MB

    8 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    750 ms · 453 KiB

    About 453 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Mobile performance score: 57

    57/100

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

  • Google Tag Manager adds 602 ms

    602 ms

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

  • Cachefly adds 172 ms

    172 ms

    Cachefly costs a phone 172 ms of main-thread work and 3.7 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 · 49 KiB

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

  • Main-thread work: 2.2 s

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

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 17 KiB

    Polyfills for old browsers add 17 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Font display

    50 ms

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

  • Phones get a much slower page than desktops

    Desktop scores 89 but mobile only 57. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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

    4 KiB

    4 KiB could be saved by minifying CSS.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 26 ms

    26 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 9.5 s

    9.5 s

    Your largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “logo 60”.

  • First Contentful Paint: 6.5 s

    6.5 s

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

  • Time to Interactive: 13.9 s

    13.9 s

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

  • Speed Index: 6.5 s

    6.5 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user FCP: 3.0 s

    3.0 s

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

  • Real-user TTFB: 1.8 s

    1.8 s

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

  • 3 images without width and height

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

6 checks passed
  • Real-user INP: 81 ms

    81 ms

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

  • Real-user CLS: 0.06

    0.06

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

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

    -13%

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

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

    -17%

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

  • Total Blocking Time: 178 ms

    178 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 5.5 MB in 97 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 97 requests on a phone: images 3.8 MB (32), scripts 1,002 KiB (26) and fonts 545 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (44 KiB) is 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 below the first screen load straight away

    1 image further down the page (44 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.6 g of CO₂ per visit

    1.56 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.56 g of CO₂e: 186.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 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 7890
  • 2 buttons without a name

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

  • Unlabelled dropdowns

    1 dropdown has no label.

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

    All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 8 links without text

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

  • 5 form fields without a label

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

  • Alternative text of images should not be repeated as text (6 elements)

    Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 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

5 to fixGoogle 8581
  • Title is long (71 characters)

    Your title is 71 characters, so Google will cut it off around 60: “Ormat Technologies Inc. - Geothermal Power | Renewable Energy Expertise”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No XML sitemap

    No XML sitemap at https://www.ormat.com/sitemap.xml, so Google discovers your pages only by following links.

  • 10 links crawlers can't follow

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

  • 5 links with vague text

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 59 internal links, 16 external

    The homepage links to 59 pages on ormat.com and 16 external pages.

5 checks passed
  • Meta description: 137 characters

    Your meta description is 137 characters: “Ormat Technologies Inc. - At Ormat Technologies, Inc. , we’re always on; delivering renewable power and energy solution…”.

  • One H1 headline

    Your main headline reads: “home page”.

  • Canonical URL set

    The canonical URL is https://www.ormat.com/en/home/a/main/.

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

AI search readiness

1 to fix88
  • 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.ormat.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.

  • Text is in the HTML

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

Other pages

2 to fix90
  • 4 pages without a meta description

    https://www.ormat.com/en/sustainability/overview/main, https://www.ormat.com/en/sustainability/report/documents, https://www.ormat.com/en/company/news/main and https://www.ormat.com/en/company/suppliers/main have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.ormat.com/en/company/news/main has no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://www.ormat.com/en/company/welcome/governance, https://www.ormat.com/en/projects/all/main, https://www.ormat.com/en/company/news/main and https://www.ormat.com/en/company/contact/main took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 24 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 10078
  • 1 broken image

    1 image failed to load on a phone, for example https://www.ormat.com/en/home/a/main/.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://ormat.cachefly.net/en/000Frames/utils/js/bootstrap/dist/css/bootstrap.min.css' fro…”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 150 words

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

  • 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
  • Clear next step on the first screen

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

  • 3 calls to action

    The homepage has 3 calls to action, for example “contact us”.

  • 2 short forms

    2 short forms (3 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

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

  • 10 other companies contacted

    Loading the homepage contacts 10 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 ormat.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 © 2019.

Stack

Hosting
Imperva

Company

Employees
763
Founded
1994
Headquarters
Reno

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on ormat.com, including 19 speed issues, 5 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