Website review, no card needed

grid-engineering.com logo

grid-engineering.com website review

Visit site (opens in a new tab)Reviewed 9 November 202630 issues · 83 checks

This review found 30 issues worth fixing on grid-engineering.com, 10 of them high impact, across 83 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
3.4 s1.9 sMay 23Nov 73.0 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.3 s
May 30, 20262.2 s
Jun 6, 20262.1 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.1 s
Jul 4, 20262.2 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.5 s
Aug 15, 20262.7 s
Aug 22, 20262.8 s
Aug 29, 20263.0 s
Sep 5, 20263.2 s
Sep 12, 20263.2 s
Nov 7, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
88 ms75 msMay 23Aug 886 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202676 ms
May 30, 202676 ms
Jun 6, 202679 ms
Jun 13, 202679 ms
Jun 20, 202679 ms
Jun 27, 202679 ms
Jul 4, 202679 ms
Jul 11, 202679 ms
Jul 18, 202685 ms
Jul 25, 202686 ms
Aug 1, 202684 ms
Aug 8, 202686 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 grid-engineering.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. grid-engineering.com at 1.5 s1.5 s
  2. grid-engineering.com at 3.1 s3.1 s
  3. grid-engineering.com at 4.6 s4.6 s
  4. grid-engineering.com at 6.1 s6.1 s
  5. grid-engineering.com at 7.7 s7.7 s
  6. grid-engineering.com at 9.2 s9.2 s
  7. grid-engineering.com at 10.7 s10.7 s
  8. grid-engineering.com at 12.2 s12.2 s

grid-engineering.com does not allow embedding, so this is Google's rendering of the page.

Speed

5 to fix85
  • Render-blocking requests

    11.3 s

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

  • Mobile performance score: 85

    85/100

    Your mobile performance score is 85. Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Clarity and Klaviyo and others), adding 855 KiB and 506 ms of main-thread time.

  • Reduce unused JavaScript

    387 KiB

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

  • Google Tag Manager adds 321 ms

    321 ms

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

  • 4 long tasks on the main thread

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

  • Use efficient cache lifetimes

    58 KiB

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

  • Minify JavaScript

    44 KiB

    44 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    24 KiB

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

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 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.

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 581 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

8 to fix50
  • 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.

  • Speed Index: 15.8 s

    15.8 s

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

  • Time to Interactive: 9.4 s

    9.4 s

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

  • Real-user LCP: 3.0 s

    3.0 s

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

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

    +35%

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

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

    1.1 s

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

  • Total Blocking Time: 223 ms

    223 ms

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

  • Tap response (INP) got 12% slower for real visitors

    +12%

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

4 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 1.7 s

    1.7 s

    Your largest element renders in 1.7 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “For all informations and support, please contact us at info…”.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.48 g

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

4 checks passed
  • Page weight: 1.7 MB in 131 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 131 requests on a phone: scripts 998 KiB (54), other files 624 KiB (65) and stylesheets 40 KiB (5). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

2 to fixGoogle 9498
  • Zoom is disabled

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

4 to fixGoogle 9277
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (16 characters)

    Your title is only 16 characters: “GRID Engineering”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No XML sitemap

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

  • Only 1 internal link

    The homepage links to only 1 page on your own site, so visitors and crawlers find few routes into the rest of it.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

4 checks passed
  • One H1 headline

    Your main headline reads: “GRID Engineering”.

  • Canonical URL set

    The canonical URL is https://grid-engineering.com/en-us/password.

  • Structured data in place

    Structured data found: BreadcrumbList.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    11%

    A phone browser shows 346 words, but the HTML your server sends has only 39. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

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

Best practices

1 to fixGoogle 9692
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

1 to fix86
  • 1 broken link to your own pages

    1 link from your homepage to your own site is broken, for example https://grid-engineering.com/admin (400).

  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • 2 redirects before the homepage

    Opening https://grid-engineering.com goes through 2 redirects before the homepage loads.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

6 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (grid-engineering.com).

  • Valid certificate (48 days left)

    The certificate from Let's Encrypt · YE2 verifies for grid-engineering.com and is valid for another 48 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://grid-engineering.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

Domain and trust

  • No CAA record

    grid-engineering.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

3 checks passed
  • Domain is 6 years old

    6 years

    grid-engineering.com was registered in Oct 2020 through Key-Systems GmbH. An established domain carries more trust with email providers and search engines.

  • DNSSEC is on

    grid-engineering.com's DNS answers are signed (DNSSEC), so they can't be forged on the way to visitors.

  • Registered until Oct 2027

    grid-engineering.com is registered until Oct 2027.

Content and conversion

4 to fix42
  • 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 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 346 words of copy

    The homepage carries about 346 words of visible text.

2 checks passed
  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

Email authentication

2 to fix60
  • DMARC is monitor-only (p=none)

    DMARC is set to p=none, so mail pretending to be grid-engineering.com is still delivered. Add a report address, check the reports, then move to quarantine.

  • No DKIM key on the usual selectors

    We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

  • Email authentication score: 60/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

1 checks passed
  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:_spf.transip.email include:_spf.odoo.com include:sim-lab.eu include:trustpilotservice.com include:_spf.g…”.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.

  • 15 cookies set on arrival

    15

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

  • 22 other companies contacted

    Loading the homepage contacts 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Apps on your store

Your storefront loads 5 apps. Each one is code from another company running for your shoppers.

None of the apps your storefront loads is on the list of apps with a known security problem.

Apps your storefront loads

Klaviyo Email Marketing Sms · Essential Announcer · Essential Announcement Bar · Zeno Sticky Cart · makeprosimp.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

  • It loads jQuery 3.4.1, older than 3.5 (which fixed known security holes).

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on grid-engineering.com, including 13 speed issues, 4 SEO issues and 4 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