Website review, no card needed

rakez.com logo

rakez.com website review

Visit site (opens in a new tab)Reviewed 18 November 202658 issues · 102 checks

This review found 58 issues worth fixing on rakez.com, 20 of them high impact, across 102 checks. The most urgent: reduce unused JavaScript. 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
2.7 s2.0 sMay 30Nov 142.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.2 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.2 s
Aug 15, 20262.3 s
Aug 22, 20262.4 s
Aug 29, 20262.5 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.5 s
Oct 31, 20262.5 s
Nov 7, 20262.5 s
Nov 14, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
422 ms222 msMay 30Nov 14291 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026399 ms
Jun 6, 2026299 ms
Jun 13, 2026246 ms
Jun 20, 2026245 ms
Jun 27, 2026255 ms
Jul 4, 2026260 ms
Jul 11, 2026270 ms
Jul 18, 2026270 ms
Jul 25, 2026262 ms
Aug 1, 2026258 ms
Aug 8, 2026254 ms
Aug 15, 2026257 ms
Aug 22, 2026261 ms
Aug 29, 2026272 ms
Sep 5, 2026281 ms
Sep 12, 2026283 ms
Sep 19, 2026282 ms
Sep 26, 2026288 ms
Oct 3, 2026285 ms
Oct 10, 2026290 ms
Oct 17, 2026293 ms
Oct 24, 2026289 ms
Oct 31, 2026288 ms
Nov 7, 2026288 ms
Nov 14, 2026291 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 rakez.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rakez.com at 1.2 s1.2 s
  2. rakez.com at 2.4 s2.4 s
  3. rakez.com at 3.6 s3.6 s
  4. rakez.com at 4.8 s4.8 s
  5. rakez.com at 6.0 s6.0 s
  6. rakez.com at 7.2 s7.2 s
  7. rakez.com at 8.4 s8.4 s
  8. rakez.com at 9.6 s9.6 s

Speed

15 to fix42
  • Reduce unused JavaScript

    1.9 s · 1.5 MB

    About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • Render-blocking requests

    3.5 s

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

  • Font display

    1.1 s

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

  • Mobile performance score: 42

    42/100

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

  • Main-thread work: 4.2 s

    A phone's processor spends 4.2 s on main-thread work while loading, 2.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 Tag Manager, Google CDN and Facebook and others), adding 2.6 MB and 1.7 s of main-thread time.

  • Google Tag Manager adds 904 ms

    904 ms

    Google Tag Manager costs a phone 904 ms of main-thread work and 1.3 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 initial server response time

    808 ms

    Reduce initial server response time. Google estimates savings of 808 ms on a phone.

  • Document request latency

    800 ms

    The HTML itself could arrive about 800 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Use efficient cache lifetimes

    350 ms · 436 KiB

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

  • Reduce unused CSS

    600 ms · 142 KiB

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

  • Minify JavaScript

    600 ms · 121 KiB

    121 KiB could be saved by minifying JavaScript.

  • Google CDN adds 275 ms

    275 ms

    Google CDN costs a phone 275 ms of main-thread work and 763 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.

  • 2,561 HTML elements

    The page has 2,561 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Server response: 908 ms

    908 ms

    Your server takes 908 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Legacy JavaScript

    250 ms · 36 KiB

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

  • 16 long tasks on the main thread

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

  • Minify CSS

    30 ms · 21 KiB

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

Core Web Vitals

12 to fix0
  • 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.

  • Largest Contentful Paint: 15.4 s

    15.4 s

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

  • Time to Interactive: 26.1 s

    26.1 s

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

  • Speed Index: 9.9 s

    9.9 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Total Blocking Time: 715 ms

    715 ms

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

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

  • Real-user INP: 274 ms

    274 ms

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

  • Real-user CLS: 0.12

    0.12

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • 13 images without width and height

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

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

    +10%

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

2 checks passed
  • Tap response (INP) got 17% faster for real visitors

    -17%

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

3 to fix53
  • Page weight: 7.1 MB in 260 requests

    7.1 MB

    Your homepage downloads 7.1 MB in 260 requests on a phone: scripts 3.1 MB (62), images 3.1 MB (101) and other files 428 KiB (74). Under 2 MB keeps phones on slow connections fast.

  • 24 images in older formats

    24 images (2.2 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.

  • 22 images below the first screen load straight away

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

  • About 2.0 g of CO₂ per visit

    2.02 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

14 to fixGoogle 5982
  • 18 buttons without a name

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

  • Invalid ARIA attributes

    11 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • 53 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

  • 6 tap targets too small

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

  • Malformed lists

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

  • 25 images without alt text

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

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

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

  • Zoom is disabled

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

  • 54 links without text

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

  • 13 form fields without a label

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

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

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

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

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

  • Headings skip levels

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

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

6 to fixGoogle 7577
  • Title is long (83 characters)

    Your title is 83 characters, so Google will cut it off around 60: “RAKEZ | Setup Your Business in Ras Al Khaimah Free Zone | Best Economic Zone in UAE”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“RAKEZ - YOUR PARTNER FOR STARTUP, SME, AND INDUST…” and “OUR STRATEGIC PILLARS”). One clear main headline is easier for people and search engines.

  • Meta description is long (169 characters)

    Your meta description is 169 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 20 links with vague text

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

  • 9 links crawlers can't follow

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

  • 92 internal links, 25 external

    The homepage links to 92 pages on rakez.com and 25 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://rakez.com/en/.

  • Structured data in place

    Structured data found: GovernmentOrganization and WebSite.

  • 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://rakez.com/sitemap.xml.

AI search readiness

100
4 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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://rakez.com/llms.txt (9 KiB, 56 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://rakez.com/en/about/rules-regulations, whose canonical is https://rakez.com/en/about-us/rules-and-regulations. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page slow to respond

    https://rakez.com/en/start-a-business/license-activity-list took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 53 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

4 to fixGoogle 7370
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97093090&tm=gtm002&Ver=2&mid=608d3409-b311-4aa4-9cb6-4a5bf5b1804a&bo=1&sid=12160d20e30d11f1977691e84e4de750&vid=12164830e30d11f1ad97035d97fd814c&vids=1&msclkid=N&gtm_t.

  • 13 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Cannot create property 'guid' on string '.dropdown-menu:not([id^="sm-"])'”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix90
  • 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.

  • A 19-field form

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

  • No map or directions link

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

  • About 2,755 words of copy

    The homepage carries about 2,755 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “START A BUSINESS” and “CONTACT US”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “start a business”, “Track your service request” and “contact us”.

  • Social proof on the page

    Social proof on the homepage: 70 testimonial or review blocks, 9 customer or partner logos and “over 30,000 companies”.

  • Analytics in place

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

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 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.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 10 trackers load before any consent

    10

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

  • 32 cookies set on arrival

    32

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

  • 30 other companies contacted

    Loading the homepage contacts 30 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 rakez.com, 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
Hosting
Imperva

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 58 issues on rakez.com, including 27 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