Website review, no card needed

edesign.com.sa logo

edesign.com.sa website review

Visit site (opens in a new tab)Reviewed 24 October 202649 issues · 81 checks

This review found 49 issues worth fixing on edesign.com.sa, 14 of them high impact, across 81 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 edesign.com.sa (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. edesign.com.sa at 1.3 s1.3 s
  2. edesign.com.sa at 2.6 s2.6 s
  3. edesign.com.sa at 3.9 s3.9 s
  4. edesign.com.sa at 5.2 s5.2 s
  5. edesign.com.sa at 6.5 s6.5 s
  6. edesign.com.sa at 7.8 s7.8 s
  7. edesign.com.sa at 9.1 s9.1 s
  8. edesign.com.sa at 10.4 s10.4 s

Speed

13 to fix34
  • Use efficient cache lifetimes

    1.7 s · 30.0 MB

    61 files are served with short cache lifetimes, so returning visitors download them again (30.0 MB).

  • Render-blocking requests

    3.8 s

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

  • Improve image delivery

    1.4 s · 733 KiB

    12 images could be 733 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

  • Mobile performance score: 34

    34/100

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

  • Main-thread work: 8.2 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, tailwindcss.com and Google Tag Manager and others), adding 2.0 MB and 2.4 s of main-thread time.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 1.3 s. During a long task the page ignores taps.

  • Google CDN adds 961 ms

    961 ms

    Google CDN costs a phone 961 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 JavaScript

    917 KiB

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

  • Font display

    700 ms

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

  • tailwindcss.com adds 514 ms

    514 ms

    tailwindcss.com costs a phone 514 ms of main-thread work and 268 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 391 ms

    391 ms

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

  • Facebook adds 348 ms

    348 ms

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

  • Reduce unused CSS

    190 ms · 33 KiB

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

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

  • Minify CSS

    8 KiB

    8 KiB could be saved by minifying CSS.

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

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

    34 ms

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

Core Web Vitals

5 to fix42
  • Speed Index: 12.2 s

    12.2 s

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

  • Time to Interactive: 16.2 s

    16.2 s

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

  • Total Blocking Time: 1.7 s

    1.7 s

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

  • Largest Contentful Paint: 5.8 s

    5.8 s

    Your largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • First Contentful Paint: 4.3 s

    4.3 s

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

  • 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

    0

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

Images and page weight

4 to fix43
  • Page weight: 32.2 MB in 95 requests

    32.2 MB

    Your homepage downloads 32.2 MB in 95 requests on a phone: media 27.9 MB (6), scripts 2.0 MB (30) and images 1.7 MB (29). Under 2 MB keeps phones on slow connections fast.

  • 15 images in older formats

    15 images (1.5 MB) are 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.

  • 4 images below the first screen load straight away

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

  • 1 image far larger than shown

    35 KiB

    1 image is downloaded at several times the size a phone draws it, for example home-blogs-section.jpeg at 1,600 px wide, shown at 390 px. Resized copies would save about 35 KiB.

  • About 9.1 g of CO₂ per visit

    9.12 g

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

Accessibility

6 to fixGoogle 7489
  • 9 tap targets too small

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

  • 8 images without alt text

    8 images have no alt text, which hurts accessibility and image search.

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

  • 14 links without text

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

  • 9 form fields without a label

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

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

1 checks passed
  • 29 automated accessibility rules passed

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

8 to fixGoogle 6770
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “EDESIGN | Digital Agency | Website | APP | Social Media | Advertising”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Digital Agency” and “Latest Blogs”). One clear main headline is easier for people and search engines.

  • No canonical URL

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

  • Meta description is long (301 characters)

    Your meta description is 301 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.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 2 links crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 36 internal links, 5 external

    The homepage links to 36 pages on edesign.com.sa and 5 external pages.

2 checks passed
  • 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.edesign.com.sa/sitemap.xml.

AI search readiness

1 to fix83
  • 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://edesign.com.sa/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.

Other pages

3 to fix86
  • 2 pages share a title

    https://edesign.com.sa/Blogs and https://edesign.com.sa/page/Blogs all use the title “Blogs”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 9 pages share a meta description

    https://edesign.com.sa/page/Request-A-Call, https://edesign.com.sa/page/About, https://edesign.com.sa/page/Work, https://edesign.com.sa/page/Services, https://edesign.com.sa/page/Careers and https://edesign.com.sa/page/Vendor and 1 other use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://edesign.com.sa/page/About, https://edesign.com.sa/Blogs and https://edesign.com.sa/page/Blogs have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://edesign.com.sa/page/Contact took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage 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.

  • Every page has a meta description

    All 15 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 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 8885
  • 11 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix57
  • 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.

  • Thin social proof

    Social proof on the homepage: 31 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 10-field form

    Your longest form asks for 10 fields (0 required). Every extra field lowers completion.

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

  • Only about 57 words

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

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

2 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Request a Call” and “Contact”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 7 cookies set on arrival

    7

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

  • 17 other companies contacted

    Loading the homepage contacts 17 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 edesign.com.sa, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

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 49 issues on edesign.com.sa, including 18 speed issues, 8 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