Website review, no card needed

amrest.eu logo

amrest.eu website review

Visit site (opens in a new tab)Reviewed 20 October 202640 issues · 87 checks

This review found 40 issues worth fixing on amrest.eu, 20 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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
2.7 s2.4 sMay 2Oct 172.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.6 s
May 9, 20262.6 s
May 16, 20262.5 s
May 23, 20262.6 s
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.6 s
Jun 20, 20262.5 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.5 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.6 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.4 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
150 ms135 msMay 2Oct 17138 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026140 ms
May 9, 2026141 ms
May 16, 2026139 ms
May 23, 2026139 ms
May 30, 2026142 ms
Jun 6, 2026142 ms
Jun 13, 2026140 ms
Jun 20, 2026141 ms
Jun 27, 2026140 ms
Jul 4, 2026140 ms
Jul 11, 2026144 ms
Jul 18, 2026146 ms
Jul 25, 2026145 ms
Aug 1, 2026145 ms
Aug 8, 2026145 ms
Aug 15, 2026145 ms
Aug 22, 2026148 ms
Aug 29, 2026146 ms
Sep 5, 2026143 ms
Sep 12, 2026143 ms
Sep 19, 2026142 ms
Sep 26, 2026139 ms
Oct 3, 2026141 ms
Oct 10, 2026137 ms
Oct 17, 2026138 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 amrest.eu (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. amrest.eu at 0.6 s0.6 s
  2. amrest.eu at 1.2 s1.2 s
  3. amrest.eu at 1.8 s1.8 s
  4. amrest.eu at 2.4 s2.4 s
  5. amrest.eu at 3.0 s3.0 s
  6. amrest.eu at 3.6 s3.6 s
  7. amrest.eu at 4.2 s4.2 s
  8. amrest.eu at 4.8 s4.8 s

Speed

10 to fix18
  • Reduce unused JavaScript

    10.2 s · 7.1 MB

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

  • Minify JavaScript

    9.0 s · 7.5 MB

    7.5 MB could be saved by minifying JavaScript.

  • Render-blocking requests

    6.8 s

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

  • Improve image delivery

    4.1 s · 1.1 MB

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

  • Reduce unused CSS

    3.3 s · 690 KiB

    About 690 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.3 s faster on a phone.

  • Use efficient cache lifetimes

    2.6 s · 536 KiB

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

  • Mobile performance score: 18

    18/100

    Your mobile performance score is 18 (desktop: 31). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Duplicated JavaScript

    450 ms · 8.8 MB

    8.8 MB JavaScript is shipped twice across bundles. Google estimates it would make the page about 450 ms faster on a phone.

  • Font display

    550 ms

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

  • Main-thread work: 2.6 s

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (piwik.pro, Google Tag Manager and Optanon and others), adding 449 KiB and 305 ms of main-thread time.

  • Legacy JavaScript

    200 ms · 64 KiB

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

  • 14 long tasks on the main thread

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

  • Document request latency

    75 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Minify CSS

    9 KiB

    9 KiB could be saved by minifying CSS.

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

1 checks passed
  • Server response: 477 ms

    477 ms

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

Core Web Vitals

11 to fix33
  • 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 CLS: 0.28

    0.28

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

  • Largest Contentful Paint: 33.9 s

    33.9 s

    Your largest element takes 33.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Service is our recipe for winning”.

  • Speed Index: 18.2 s

    18.2 s

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

  • Time to Interactive: 82.7 s

    82.7 s

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

  • First Contentful Paint: 7.3 s

    7.3 s

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

  • Cumulative Layout Shift: 0.469

    0.469

    The layout shifts by 0.469 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 645 ms

    645 ms

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user TTFB: 899 ms

    899 ms

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

  • 10 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

2 checks passed
  • Real-user INP: 150 ms

    150 ms

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

  • Real-user FCP: 1.7 s

    1.7 s

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

Images and page weight

1 to fix70
  • Page weight: 17.4 MB in 88 requests

    17.4 MB

    Your homepage downloads 17.4 MB in 88 requests on a phone: scripts 14.4 MB (37), images 1.7 MB (26) and stylesheets 708 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

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

  • About 4.9 g of CO₂ per visit

    4.94 g

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

6 to fixGoogle 8492
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 3 text elements with low contrast

    3 text elements don'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.

  • 3 links without text

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

  • 1 form field without a label

    1 form field has 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).

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 48 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: 48 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 8578
  • Title is short (13 characters)

    Your title is only 13 characters: “Home | AmRest”. 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 (209 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 10 links crawlers can't follow

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

  • 8 links with vague text

    8 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 incomplete here.

  • 82 internal links, 2 external

    The homepage links to 82 pages on amrest.eu and 2 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Service is our recipe for winning”.

  • Canonical URL set

    The canonical URL is https://www.amrest.eu/en.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.amrest.eu/sitemap.xml.

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.amrest.eu/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 (811 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 8 pages without a meta description

    https://www.amrest.eu/en/our-brands/bacoa, https://www.amrest.eu/en/our-brands/blue-frog, https://www.amrest.eu/en/our-brands/burger-king, https://www.amrest.eu/en/our-brands/kfc, https://www.amrest.eu/en/our-brands/la-tagliatella and https://www.amrest.eu/en/our-brands/pizza-hut and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://www.amrest.eu/en/about-us/vision-strategy-and-culture, https://www.amrest.eu/en/about-us/reports, https://www.amrest.eu/en/our-brands and https://www.amrest.eu/en/investors/investors-and-shareholders have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 57 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 8197
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

    The homepage carries about 627 words of visible text.

4 checks passed
  • Clear next step on the first screen

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

  • 6 calls to action

    The homepage has 6 calls to action, for example “Sushi Shop”, “Investor relations contact” and “Media contact”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies (measured from a US location before any click).

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 amrest.eu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Drupal
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Azure

Company

Founded
1993
Headquarters
Wrocław

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on amrest.eu, including 21 speed issues, 6 SEO issues and 2 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