Website review, no card needed

endress-group.ro logo

endress-group.ro website review

Visit site (opens in a new tab)Reviewed 20 October 202634 issues · 77 checks

This review found 34 issues worth fixing on endress-group.ro, 13 of them high impact, across 77 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

Full-page screenshot of endress-group.ro (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. endress-group.ro at 0.8 s0.8 s
  2. endress-group.ro at 1.5 s1.5 s
  3. endress-group.ro at 2.3 s2.3 s
  4. endress-group.ro at 3.0 s3.0 s
  5. endress-group.ro at 3.8 s3.8 s
  6. endress-group.ro at 4.5 s4.5 s
  7. endress-group.ro at 5.3 s5.3 s
  8. endress-group.ro at 6.0 s6.0 s

Speed

8 to fix56
  • Render-blocking requests

    4.3 s

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

  • Improve image delivery

    300 ms · 3.4 MB

    9 images could be 3.4 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.

  • Reduce unused JavaScript

    450 ms · 751 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.5 MB and 881 ms of main-thread time.

  • Mobile performance score: 56

    56/100

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

  • Google CDN adds 656 ms

    656 ms

    Google CDN costs a phone 656 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.

  • Reduce unused CSS

    450 ms · 120 KiB

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

  • Main-thread work: 3.9 s

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

  • 12 long tasks on the main thread

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

  • Font display

    150 ms

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

  • Phones get a much slower page than desktops

    Desktop scores 87 but mobile only 56. 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.

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

5 to fix63
  • Time to Interactive: 29.9 s

    29.9 s

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

  • Largest Contentful Paint: 6.2 s

    6.2 s

    Your largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SOLUȚII DE SUCCES Endress Zenessis Group Profesioniști în S…”.

  • Speed Index: 8.3 s

    8.3 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Total Blocking Time: 311 ms

    311 ms

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0.004

    0.004

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

Images and page weight

1 to fix70
  • Page weight: 7.8 MB in 134 requests

    7.8 MB

    Your homepage downloads 7.8 MB in 134 requests on a phone: images 4.9 MB (15), scripts 1.5 MB (50) and other files 695 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (68 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.

  • 2 images below the first screen load straight away

    2 images further down the page (96 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.2 g of CO₂ per visit

    2.20 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.20 g of CO₂e: 264.5 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

7 to fixGoogle 8589
  • 35 tap targets too small

    35 tap targets are too small or too close together to hit reliably with a finger.

  • 8 text elements with low contrast

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

  • Form elements should have a visible label (2 elements)

    Form elements should have a visible label: 2 elements on the page fail this check, rated serious by axe-core.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

  • 13 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 36 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

2 to fixGoogle 10088
  • Title is long (88 characters)

    Your title is 88 characters, so Google will cut it off around 60: “Endress Group România - Standarde noi în tehnologie și inovație în industria industrială”.

  • Meta description is long (261 characters)

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

  • 26 internal links, 11 external

    The homepage links to 26 pages on endress-group.ro and 11 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Endress Zenessis Group Profesioniști în Soluții Tehnice Avansate”.

  • Canonical URL set

    The canonical URL is https://endress-group.ro/.

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and WebPage.

  • 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://endress-group.ro/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing url, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://endress-group.ro/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 (976 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix52
  • 1 linked page is broken

    Your homepage links to https://endress-group.ro/dezvoltarea-endress-group-romania-srl-prin-achizitie-utilaje-si-construire-hala-parter-pentrumontaj-echipamente-electrice, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages point its canonical at the homepage

    https://endress-group.ro/en/home and https://endress-group.ro/acasa 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.

  • 6 pages share a title

    /, https://endress-group.ro/acasa, https://endress-group.ro/anunt-intentie-obtinere-autorizatie-mediu, https://endress-group.ro/anunt-construire-doua-hale, https://endress-group.ro/anunt-demolare-corp-c1 and https://endress-group.ro/anunt-construire-hala-c13 all use the title “Endress Group România - Standarde noi în tehnologie și inovație în in…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages share a meta description

    https://endress-group.ro/acasa, https://endress-group.ro/anunt-intentie-obtinere-autorizatie-mediu, https://endress-group.ro/anunt-construire-doua-hale, https://endress-group.ro/anunt-demolare-corp-c1 and https://endress-group.ro/anunt-construire-hala-c13 use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://endress-group.ro/anunt-intentie-obtinere-autorizatie-mediu, https://endress-group.ro/anunt-construire-doua-hale, https://endress-group.ro/anunt-demolare-corp-c1 and https://endress-group.ro/anunt-construire-hala-c13 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://endress-group.ro/anunt-intentie-obtinere-autorizatie-mediu, https://endress-group.ro/anunt-construire-doua-hale, https://endress-group.ro/anunt-demolare-corp-c1 and https://endress-group.ro/anunt-construire-hala-c13 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.

  • 10 internal pages checked

    We fetched 10 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Every page has a meta description

    All 6 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 5 small tap targets

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

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

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

  • A 8-field form

    Your longest form asks for 8 fields (7 required). Every extra field lowers completion.

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

  • About 838 words of copy

    The homepage carries about 838 words of visible text.

5 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “CONTACT” and “Contact”.

  • Social proof on the page

    Social proof on the homepage: 2 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 30 phone links and 14 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
  • 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.

  • 3 cookies set on arrival

    3

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 endress-group.ro, 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

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 endress-group.ro, including 13 speed issues, 2 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