Website review, no card needed

edelbussys.com logo

edelbussys.com website review

Visit site (opens in a new tab)Reviewed 7 November 202630 issues · 66 checks

This review found 30 issues worth fixing on edelbussys.com, 6 of them high impact, across 66 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

Full-page screenshot of edelbussys.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. edelbussys.com at 0.4 s0.4 s
  2. edelbussys.com at 0.8 s0.8 s
  3. edelbussys.com at 1.1 s1.1 s
  4. edelbussys.com at 1.5 s1.5 s
  5. edelbussys.com at 1.9 s1.9 s
  6. edelbussys.com at 2.3 s2.3 s
  7. edelbussys.com at 2.6 s2.6 s
  8. edelbussys.com at 3.0 s3.0 s

Speed

7 to fix74
  • Use efficient cache lifetimes

    1.3 s · 147 KiB

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

  • Mobile performance score: 74

    74/100

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

  • Reduce unused JavaScript

    450 ms · 95 KiB

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

  • Render-blocking requests

    450 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 450 ms.

  • Reduce unused CSS

    300 ms · 58 KiB

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

  • 7 long tasks on the main thread

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

  • Main-thread work: 2.1 s

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

  • Improve image delivery

    150 ms · 50 KiB

    1 image could be 50 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 5 third-party services on the page

    5 third-party services load with your homepage (yolacdn.net, sitewit.com and Cloudflare CDN and others), adding 70 KiB and 90 ms of main-thread time.

  • Legacy JavaScript

    7 KiB

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

  • 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: 41 ms

    41 ms

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

Core Web Vitals

5 to fix71
  • Total Blocking Time: 524 ms

    524 ms

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

  • Largest Contentful Paint: 3.7 s

    3.7 s

    Your largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is element render delay (1.5 s).

  • Time to Interactive: 4.6 s

    4.6 s

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

  • Speed Index: 3.8 s

    3.8 s

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

  • 1 image without width and height

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

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

2 checks passed
  • First Contentful Paint: 1.2 s

    1.2 s

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

  • Cumulative Layout Shift: 0.012

    0.012

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

Images and page weight

100
  • About 0.1 g of CO₂ per visit

    0.13 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.13 g of CO₂e: 15.6 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: 470 KiB in 19 requests

    470 KiB

    Your homepage downloads 470 KiB in 19 requests on a phone: scripts 176 KiB (5), images 168 KiB (6) and stylesheets 73 KiB (2). 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

4 to fixGoogle 8493
  • 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.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 13 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.

  • Headings skip levels

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

1 checks passed
  • 42 automated accessibility rules passed

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

7 to fixGoogle 8368
  • No meta description

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

  • Title is short (4 characters)

    Your title is only 4 characters: “Home”. 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.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

  • Only 2 internal links

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

3 checks passed
  • One H1 headline

    Your main headline reads: “Reliable computer solutions”.

  • 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://www.edelbussys.com/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.edelbussys.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 (245 words), so crawlers that don't run JavaScript still read it.

Best practices

1 to fixGoogle 10092
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix56
  • 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 social proof

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 244 words

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Pricing” and “Contact”.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 2 of them by other companies (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.

  • 5 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

Hosting
AWS

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 edelbussys.com, including 12 speed issues, 7 SEO issues and 5 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