Website review, no card needed

alkoutprojects.com logo

alkoutprojects.com website review

Visit site (opens in a new tab)Reviewed 19 October 202645 issues · 102 checks

This review found 45 issues worth fixing on alkoutprojects.com, 16 of them high impact, across 102 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

Real-visitor load time (LCP)75th percentile, phones
4.1 s2.8 sApr 25Sep 262.9 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20264.0 s
May 23, 20263.2 s
Jun 6, 20263.1 s
Jun 13, 20263.1 s
Aug 15, 20263.2 s
Aug 22, 20263.3 s
Aug 29, 20263.3 s
Sep 5, 20263.3 s
Sep 12, 20263.2 s
Sep 19, 20263.0 s
Sep 26, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
131 ms86 msJun 6Sep 1991 ms
Show as table
DateReal-visitor tap response (INP)
Jun 6, 202694 ms
Jun 13, 2026103 ms
Aug 22, 2026103 ms
Aug 29, 2026126 ms
Sep 5, 2026112 ms
Sep 12, 202694 ms
Sep 19, 202691 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

Live view · interaction off

Speed

6 to fix54
  • Use efficient cache lifetimes

    17.3 s · 3.8 MB

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

  • Improve image delivery

    11.7 s · 2.5 MB

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

  • Render-blocking requests

    4.2 s

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

  • Reduce unused JavaScript

    900 ms · 204 KiB

    About 204 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Mobile performance score: 54

    54/100

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

  • Reduce unused CSS

    450 ms · 120 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, GoDaddy and iconify.design and others), adding 346 KiB and 290 ms of main-thread time.

  • Minify JavaScript

    150 ms · 27 KiB

    27 KiB could be saved by minifying JavaScript.

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    24 KiB

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

  • Minify CSS

    6 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 1.9 s

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

6 to fix62
  • Largest Contentful Paint: 22.9 s

    22.9 s

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

  • Time to Interactive: 23.0 s

    23.0 s

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

  • Speed Index: 11.5 s

    11.5 s

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

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • 16 images without width and height

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

  • Cumulative Layout Shift: 0.101

    0.101

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

  • Tap response (INP) held steady for real visitors

    -6%

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

  • 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
  • Largest content (LCP) got 17% faster for real visitors

    -17%

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

  • Total Blocking Time: 121 ms

    121 ms

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

Images and page weight

5 to fix18
  • Page weight: 4.3 MB in 93 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 93 requests on a phone: images 3.5 MB (31), scripts 556 KiB (30) and stylesheets 300 KiB (23). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 2.3 MB together. On a phone connection a single image that size takes seconds.

  • 8 images far larger than shown

    1,016 KiB

    8 images are downloaded at several times the size a phone draws them, for example footer_image_crop.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 1,016 KiB.

  • 11 images in older formats

    11 images (3.1 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.

  • 2 images below the first screen load straight away

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

  • About 1.2 g of CO₂ per visit

    1.23 g

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

Accessibility

11 to fixGoogle 7384
  • 3 buttons without a name

    3 buttons have no accessible name, so screen readers announce just “button”.

  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 10 images without alt text

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

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

    All page content should be contained by landmarks: 2 elements on the page fail 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.

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

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

  • 37 links without text

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

  • ARIA role should be appropriate for the element (2 elements)

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

  • Elements marked as presentational should be consistently ignored (2 elements)

    Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 35 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 11 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 7765
  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (15 characters)

    Your title is only 15 characters: “Alkout Projects”. 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.

  • 25 links with vague text

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

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

  • No X (Twitter) card tag

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

  • 117 internal links, 0 external

    The homepage links to 117 pages on alkoutprojects.com and 0 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://alkoutprojects.com/.

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

Other pages

2 to fix90
  • 15 pages without a meta description

    /about-us/company-overview, /about-us/our-history, /about-us/our-subsidiaries, /about-us/board-of-directors, /about-us/executive-management and /about-us/organizational-chart and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    /about-us/company-overview, /about-us/our-history, /about-us/our-subsidiaries, /about-us/board-of-directors, /about-us/executive-management and /about-us/organizational-chart and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    /about-us/board-of-directors, /about-us/executive-management and /industries/pharmaceuticals took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 to fixGoogle 9285
  • 20 small tap targets

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

  • 2 JavaScript errors while loading

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

  • 24 distorted images

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

2 to fix86
  • No HSTS header

    No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

  • No Content-Security-Policy

    No Content-Security-Policy header, the main browser-side defence against injected scripts.

  • No clickjacking protection

    Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

  • No X-Content-Type-Options

    X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

  • No Referrer-Policy

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

  • No security.txt

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

5 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (alkoutprojects.com).

  • Valid certificate (180 days left)

    The certificate from GoDaddy.com · GoDaddy TLS Intermediate CA DV - R1v1 verifies for alkoutprojects.com and is valid for another 180 days.

  • http:// redirects to https

    http://alkoutprojects.com redirects to the secure version.

  • HTTP/2

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

  • All 40 links work

    All 40 links checked from your homepage (40 internal, 0 external) answered without errors.

Domain and trust

  • No CAA record

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

  • DNSSEC is off

    alkoutprojects.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

2 checks passed
  • Domain is 19 years old

    19 years

    alkoutprojects.com was registered in Apr 2007 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.

  • Registered until Apr 2027

    alkoutprojects.com is registered until Apr 2027.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 879 words of visible text.

3 checks passed
  • Clear next step on the first screen

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

  • 2 calls to action

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

  • Analytics in place

    Analytics detected: Google Analytics.

Email authentication

90
  • Email authentication score: 90/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.

3 checks passed
  • DMARC policy: quarantine

    DMARC tells receivers to quarantine mail that fails authentication.

  • SPF with a strict ending (-all)

    An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 +a +mx +ip4:5.79.80.155 +ip4:168.187.78.105 +a:dispatch-eu.ppe-hosted.com +include:spf.protection.outlook.com -a…”.

  • DKIM signing found

    A DKIM key is published (selector “selector2”, “s1” and “s2”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 5 cookies set on arrival

    5

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

  • 12 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2022.
  • 2 plugins are behind their latest release.date-time-picker-for-contact-form-7 1.0.0 → 1.1.1 · contact-form-7 6.1.7 → 6.2.2

Stack

CMS
WordPress 7.1.3
Framework
jQuery
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This free review found 45 issues on alkoutprojects.com, including 12 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