Website review, no card needed

grill.se logo

grill.se website review

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

This review found 36 issues worth fixing on grill.se, 17 of them high impact, across 87 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
5.3 s2.6 sMay 2Oct 174.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.1 s
May 9, 20263.1 s
May 16, 20263.1 s
May 23, 20263.1 s
May 30, 20263.2 s
Jun 6, 20263.2 s
Jun 13, 20263.1 s
Jun 20, 20262.9 s
Jun 27, 20263.1 s
Jul 4, 20263.4 s
Jul 11, 20263.8 s
Jul 18, 20263.9 s
Jul 25, 20263.9 s
Aug 1, 20263.7 s
Aug 8, 20263.8 s
Aug 15, 20263.9 s
Aug 22, 20264.3 s
Aug 29, 20264.8 s
Sep 5, 20265.0 s
Sep 12, 20264.8 s
Sep 19, 20265.0 s
Sep 26, 20264.9 s
Oct 3, 20264.6 s
Oct 10, 20264.8 s
Oct 17, 20264.5 s
Real-visitor tap response (INP)75th percentile, phones
164 ms106 msMay 2Oct 17155 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026155 ms
May 9, 2026157 ms
May 16, 2026156 ms
May 23, 2026147 ms
May 30, 2026145 ms
Jun 6, 2026137 ms
Jun 13, 2026132 ms
Jun 20, 2026133 ms
Jun 27, 2026130 ms
Jul 4, 2026132 ms
Jul 11, 2026134 ms
Jul 18, 2026133 ms
Jul 25, 2026129 ms
Aug 1, 2026127 ms
Aug 8, 2026120 ms
Aug 15, 2026115 ms
Aug 22, 2026113 ms
Aug 29, 2026117 ms
Sep 5, 2026120 ms
Sep 12, 2026120 ms
Sep 19, 2026129 ms
Sep 26, 2026133 ms
Oct 3, 2026141 ms
Oct 10, 2026152 ms
Oct 17, 2026155 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 grill.se (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. grill.se at 1.0 s1.0 s
  2. grill.se at 2.0 s2.0 s
  3. grill.se at 3.0 s3.0 s
  4. grill.se at 4.0 s4.0 s
  5. grill.se at 5.0 s5.0 s
  6. grill.se at 6.0 s6.0 s
  7. grill.se at 7.0 s7.0 s
  8. grill.se at 8.0 s8.0 s

Speed

8 to fix61
  • Render-blocking requests

    3.0 s

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

  • Use efficient cache lifetimes

    1.6 s · 304 KiB

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

  • Reduce unused JavaScript

    1.1 s · 267 KiB

    About 267 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Font display

    1.1 s

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

  • Improve image delivery

    2.1 MB

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

  • Mobile performance score: 61

    61/100

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

  • Facebook adds 191 ms

    191 ms

    Facebook costs a phone 191 ms of main-thread work and 344 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.

  • Google Tag Manager adds 94 ms

    94 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Facebook, Google Tag Manager and cdn-cookieyes.com and others), adding 885 KiB and 313 ms of main-thread time.

  • Legacy JavaScript

    250 ms · 12 KiB

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

  • 4 long tasks on the main thread

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

  • Reduce unused CSS

    74 KiB

    About 74 KiB of CSS is downloaded but never applied on this page.

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.6 s

    A phone's processor spends 1.6 s on main-thread work while loading, 758 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

10 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: 4.6 s

    4.6 s

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

  • Real-user FCP: 4.0 s

    4.0 s

    Real visitors see the first content after 4.0 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.

  • Largest Contentful Paint: 14.2 s

    14.2 s

    Your largest element takes 14.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “..................................... BOKA BORD SE MENYN”.

  • Time to Interactive: 14.3 s

    14.3 s

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

  • Speed Index: 9.1 s

    9.1 s

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

  • Largest content (LCP) got 49% slower for real visitors

    +49%

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 21 images without width and height

    21 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 155 ms to 155 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user INP: 162 ms

    162 ms

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

  • Real-user CLS: 0.07

    0.07

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

  • Cumulative Layout Shift: 0.096

    0.096

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

  • Total Blocking Time: 111 ms

    111 ms

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

Images and page weight

3 to fix43
  • Page weight: 7.9 MB in 104 requests

    7.9 MB

    Your homepage downloads 7.9 MB in 104 requests on a phone: media 3.4 MB (2), images 2.8 MB (15) and scripts 1.1 MB (37). Under 2 MB keeps phones on slow connections fast.

  • 10 images far larger than shown

    1.3 MB

    10 images are downloaded at several times the size a phone draws them, for example fredag-vecka-30-16.jpg at 2,048 px wide, shown at 349 px. Resized copies would save about 1.3 MB.

  • 6 images below the first screen load straight away

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

  • 1 image in older formats

    1 image (54 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 2.2 g of CO₂ per visit

    2.23 g

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

Accessibility

9 to fixGoogle 9691
  • 14 text elements with low contrast

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

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

    All page content should be contained by landmarks: 29 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 (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails 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.

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

Google 100100
  • 13 internal links, 17 external

    The homepage links to 13 pages on grill.se and 17 external pages.

8 checks passed
  • Meta description: 136 characters

    Your meta description is 136 characters: “Välkommen till Restaurang Grill, vi är en köttrestaurang i centrala Stockholm. Här hittar ni sju olika matsalar under e…”.

  • One H1 headline

    Your main headline reads: “Restaurang Grill - Bar & köttrestaurang stockholm”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Restaurang Grill - Köttrestaurang i Stockholm”.

  • Canonical URL set

    The canonical URL is https://grill.se/.

  • Structured data in place

    Structured data found: AboutPage, ImageObject, Organization, Place and Restaurant.

  • 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://grill.se/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://grill.se/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.

3 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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://grill.se/cookie-policy is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without an H1

    https://grill.se/cookie-policy has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://grill.se/jobba-pa-grill has 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.

  • 4 internal pages checked

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

5 checks passed
  • Linked pages load

    All 4 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 4 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 4 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 734 words of visible text.

5 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 3 trackers load before any consent

    3

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

  • 4 cookies set on arrival

    4

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

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 grill.se, 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 © 2023.

Stack

CMS
WordPress
Framework
jQuery
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 36 issues on grill.se, including 18 speed 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