Website review, no card needed

alraimedia.com logo

alraimedia.com website review

Visit site (opens in a new tab)Reviewed 19 October 202643 issues · 85 checks

This review found 43 issues worth fixing on alraimedia.com, 22 of them high impact, across 85 checks. The most urgent: improve image delivery. 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.3 s1.6 sMay 2Oct 171.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.9 s
May 9, 20261.8 s
May 16, 20261.9 s
May 23, 20261.9 s
May 30, 20262.0 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.0 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
159 ms115 msMay 2Oct 17127 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026142 ms
May 9, 2026137 ms
May 16, 2026137 ms
May 23, 2026135 ms
May 30, 2026142 ms
Jun 6, 2026150 ms
Jun 13, 2026152 ms
Jun 20, 2026154 ms
Jun 27, 2026150 ms
Jul 4, 2026134 ms
Jul 11, 2026128 ms
Jul 18, 2026124 ms
Jul 25, 2026120 ms
Aug 1, 2026126 ms
Aug 8, 2026124 ms
Aug 15, 2026125 ms
Aug 22, 2026124 ms
Aug 29, 2026123 ms
Sep 5, 2026121 ms
Sep 12, 2026122 ms
Sep 19, 2026122 ms
Sep 26, 2026123 ms
Oct 3, 2026127 ms
Oct 10, 2026125 ms
Oct 17, 2026127 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 alraimedia.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alraimedia.com at 1.2 s1.2 s
  2. alraimedia.com at 2.5 s2.5 s
  3. alraimedia.com at 3.7 s3.7 s
  4. alraimedia.com at 5.0 s5.0 s
  5. alraimedia.com at 6.2 s6.2 s
  6. alraimedia.com at 7.5 s7.5 s
  7. alraimedia.com at 8.7 s8.7 s
  8. alraimedia.com at 9.9 s9.9 s

Speed

9 to fix24
  • Improve image delivery

    24.6 s · 4.4 MB

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

  • Reduce unused JavaScript

    5.3 s · 1.4 MB

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

  • Google/Doubleclick Ads adds 3.5 s

    3.5 s

    Google/Doubleclick Ads costs a phone 3.5 s of main-thread work and 2.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Use efficient cache lifetimes

    1.1 s · 455 KiB

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

  • Main-thread work: 13.0 s

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

  • Mobile performance score: 24

    24/100

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

  • 3,407 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google/Doubleclick Ads, Google Tag Manager and adtrafficquality.google and others), adding 3.3 MB and 4.1 s of main-thread time.

  • Google Tag Manager adds 355 ms

    355 ms

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

  • 20 long tasks on the main thread

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

  • Render-blocking requests

    150 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

  • Phones get a much slower page than desktops

    Desktop scores 57 but mobile only 24. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

    8 ms

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

Core Web Vitals

8 to fix67
  • 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: 34.1 s

    34.1 s

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

  • Time to Interactive: 46.2 s

    46.2 s

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

  • Speed Index: 13.0 s

    13.0 s

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

  • First Contentful Paint: 5.1 s

    5.1 s

    The first text or image appears after 5.1 s on a phone. Good is under 1.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.

  • Real-user CLS: 0.14

    0.14

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

  • Cumulative Layout Shift: 0.14

    0.14

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

5 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 128 ms

    128 ms

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

  • Real-user FCP: 1.0 s

    1.0 s

    Real visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 471 ms

    471 ms

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

  • Tap response (INP) got 10% faster for real visitors

    -10%

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

Images and page weight

4 to fix25
  • Page weight: 12.8 MB in 304 requests

    12.8 MB

    Your homepage downloads 12.8 MB in 304 requests on a phone: images 8.9 MB (105), scripts 2.7 MB (57) and fonts 483 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • 6 images over 500 KB

    6 images weigh 3.7 MB together. On a phone connection a single image that size takes seconds.

  • 8 images far larger than shown

    2.4 MB

    8 images are downloaded at several times the size a phone draws them, for example 2292297.jpeg at 1,200 px wide, shown at 165 px. Resized copies would save about 2.4 MB.

  • 8 images in older formats

    8 images (4.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.

  • About 3.6 g of CO₂ per visit

    3.64 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

10 to fixGoogle 7489
  • Form elements must have labels (1 element)

    Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.

  • Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

    Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

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

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

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

  • 5 links without text

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

  • 4 tap targets too small

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

  • Orphan list items

    Some list items are not inside a list.

  • 2 text elements with low contrast

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

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

2 checks passed
  • Every image has alt text

    All 23 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Title is short (16 characters)

    Your title is only 16 characters: “الراي - الرئيسية”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (49 characters)

    Your meta description is only 49 characters: “أخبار يومية سياسية اقتصادية رياضية منوعة-الرئيسية”. 70 to 160 characters is enough to sell the click.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 158 internal links, 8 external

    The homepage links to 158 pages on alraimedia.com and 8 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “صحيفة الرأي - الصفحة الرئيسية”.

  • Canonical URL set

    The canonical URL is https://www.alraimedia.com/.

  • Structured data in place

    Structured data found: WebPage.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.alraimedia.com/sitemaps/sitemap_0.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://www.alraimedia.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.

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

1 to fix90
  • 1 page points its canonical at the homepage

    https://www.alraimedia.com/newspaper/pdf declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 14 pages with very little text

    https://www.alraimedia.com/%D8%A7%D9%84%D8%A7%D8%B4%D8%AA%D8%B1%D8%A7%D9%83, https://www.alraimedia.com/%D8%A7%D9%84%D8%A5%D8%B9%D9%84%D8%A7%D9%86, https://www.alraimedia.com/careers, https://www.alraimedia.com/capital-increase-subscription-ar, https://www.alraimedia.com/%D9%88%D9%81%D9%8A%D8%A7%D8%AA and https://www.alraimedia.com/%D8%A7%D9%84%D8%B5%D9%81%D8%AD%D8%A9-%D8%A7%D9%84%D8%B1%D8%A6%D9%8A%D8%B3%D9%8A%D8%A9 and 8 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 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

2 to fixGoogle 9687
  • 15 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of undefined (reading 'addEventListener')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Only about 4 words

    The homepage has only about 4 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
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and TikTok Pixel.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Microsoft Clarity and 1 more (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies (measured from a US location before any click).

  • 33 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

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 alraimedia.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
Bootstrap
Analytics
Google Tag Manager

Company

Founded
1961
Headquarters
Kuwait

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on alraimedia.com, including 17 speed issues, 3 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