Scanned sites / alomran.info / 2026-09-27-1154

alomran.info scan from 9/27/2026, 11:54:58 AM

Scan 2026-09-27-1154

Scanned 9/27/2026, 11:54:58 AM, finished 9/27/2026, 6:06:47 PM

Site: https://alomran.info/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

80/ 100Good

On September 27, 2026 the Site Spider crawled 649 pages and 2553 assets of alomran.info, starting from https://alomran.info/. It scored 80 out of 100, a good result. 6 of 16 checks found something to fix, led by heavy assets (139), sitemap coverage (633), meta descriptions (400); 7 checks passed. Most of the points went to heavy assets (−6), sitemap coverage (−5.9), meta descriptions (−5). 3 checks found something the score does not count, listed as noted. The list below shows each check's result, the fix plan, when present, explains what to do first, and the security review at the end of the page covers headers, transport, libraries and exposed files.

Security review: Medium2 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
649
Assets fetched
2553
Status
Completed
Checks with issues
6 of 16
CoverageJob finished, partial coverage

3,202 of 3,210 discovered URLs were fetched, 13,112 left out by the 5,000-page and 1,000-asset budget. The job finished, but the crawl did not reach everything it found. HTML only: nothing here ran JavaScript. 300 link destinations on other sites were checked, 1898 left unchecked.

  • Title tags224 issues
    224 of 633 pages have title issues. 6 noindex or canonicalized pages excluded.
    −3.5 points
  • Meta descriptions400 issues
    400 of 633 pages have meta description issues. 6 noindex or canonicalized pages excluded.
    −5 points
  • HeadingsOK
    0 of 633 pages have heading issues. 6 noindex or canonicalized pages excluded.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites640 noted
    0 destinations answered with an error, 5 could not be determined (timeouts, rate limits or refusals), 1898 were left unchecked by the per-scan cap, of 300 destinations checked.
  • Redirects10 issues
    11 redirecting URLs, 0 of them chained.
    −0.1 points
  • Non-200 responses11 noted
    11 URLs did not return a 2xx response. 10 of them are pages, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 633 indexable pages have indexability warnings. 6 pages noindex by design.
  • Image alt textOK
    0 of 15714 image references have no alt attribute. 6779 use an empty alt (decorative), which is fine.
  • Heavy assets139 issues
    139 assets larger than 500 KB among 2553 fetched assets. 3 documents over that size are listed but not counted: downloads are not page weight.
    −6 points
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
  • Sitemap coverage633 issues
    1 sitemap listing 0 URLs: 633 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −5.9 points
  • Internal link countsOK
    Internal link counts for 500 pages.
  • Thin contentOK
    0 of 633 pages have fewer than 200 words. 6 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1336 sites, median 80%, average 79%

alomran.info scores 80%, higher than 46% of the 1336 scanned sites. See the full ranking.

037730%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 0 sites10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 0 sites15%: 0 sites16%: 0 sites17%: 0 sites18%: 0 sites19%: 0 sites20%: 0 sites21%: 1 site22%: 0 sites23%: 0 sites24%: 0 sites25%: 0 sites26%: 0 sites27%: 0 sites28%: 1 site29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 0 sites34%: 0 sites35%: 1 site36%: 1 site37%: 1 site38%: 1 site39%: 0 sites40%: 1 site41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 2 sites46%: 2 sites47%: 2 sites48%: 2 sites49%: 2 sites50%: 3 sites51%: 5 sites52%: 6 sites53%: 5 sites54%: 5 sites55%: 4 sites56%: 3 sites57%: 5 sites58%: 9 sites59%: 5 sites60%: 8 sites61%: 10 sites62%: 14 sites63%: 11 sites64%: 8 sites65%: 14 sites66%: 14 sites67%: 26 sites68%: 24 sites69%: 14 sites70%: 32 sites71%: 29 sites72%: 37 sites73%: 33 sites74%: 41 sites75%: 37 sites76%: 49 sites77%: 45 sites78%: 57 sites79%: 48 sites80%: 66 sites81%: 73 sites82%: 67 sites83%: 61 sites84%: 61 sites85%: 45 sites86%: 49 sites87%: 48 sites88%: 49 sites89%: 36 sites90%: 28 sites91%: 31 sites92%: 18 sites93%: 8 sites94%: 10 sites95%: 5 sites96%: 7 sites97%: 3 sites98%: 1 site99%: 2 sites100%: 50 sites80% here100%90%80%70%60%50%40%30%20%10%0%

Green 90% and up (Excellent), lime 75 to 89 (Good), amber 50 to 74 (Needs work), red below 50 (Poor).

Internal link map

Loading the link map...

Start page (centre)OKRedirectErrorOrphanLinked from most pagesOne inbound link or noneRings = clicks from the start page. Size = inbound links. Drag to pan, scroll to zoom, click a page to see only its links.

Fix plan

Written by gpt-4o-mini from the scan findings

Your website has some important SEO issues that need fixing, particularly with redirects, titles, meta descriptions, heavy assets, and sitemap coverage. Addressing these will enhance your site's performance and visibility.

  1. 1

    Fix Redirects

    Why: Redirects can confuse search engines and impair user experience.

    How: Update or remove unnecessary redirects to ensure URLs resolve directly.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: Non-200 responses can lead to lost traffic and poor user experience.

    How: Ensure all pages return a 200 status or correct faulty redirects.

    Checks: status-codes

  3. 3

    Improve Title Tags

    Why: Proper title tags are crucial for SEO and user engagement.

    How: Rewrite titles to ensure they are unique, descriptive, and within recommended length.

    Checks: titles

  4. 4

    Add and Optimize Meta Descriptions

    Why: Meta descriptions help improve click-through rates in search results.

    How: Provide unique and concise meta descriptions for affected pages.

    Checks: meta-descriptions

  5. 5

    Optimize Heavy Assets

    Why: Large assets can slow down page load times, affecting SEO.

    How: Compress or resize images over 500 KB or consider alternative methods for downloads.

    Checks: heavy-assets

  6. 6

    Update Sitemap Coverage

    Why: A comprehensive sitemap is essential for indexing by search engines.

    How: Check sitemap settings to include all crawled pages and submit it to search engines.

    Checks: sitemap-coverage

Generated automatically; verify each change against your own site before relying on it.

Security review

Written by gpt-4o-mini from 16 checks over the crawl

The website alomran.info has several security issues that need addressing to protect user data and mitigate risks. Key findings include the absence of HTTP Strict Transport Security (HSTS) and missing security headers on critical resources. Immediate action is recommended to enhance the site’s security posture.

  • 0 high
  • 2 medium
  • 2 low
  • 1 info
  1. 1

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users typing the address without HTTPS can be intercepted on their first request.

    Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains

    Evidence: HTTP Strict Transport Security

  2. 2

    Lack of HttpOnly and SameSite flags on cookiesMedium

    Why it matters: Cookies without protective flags are vulnerable to theft and misuse by scripts.

    Fix: Set HttpOnly, Secure, and SameSite='Lax' on all cookies.

    Evidence: Cookie flags

  3. 3

    Missing X-Content-Type-Options headerLow

    Why it matters: Without this header, browsers can execute files incorrectly based on their contents.

    Fix: Add the header: X-Content-Type-Options: nosniff

    Evidence: MIME sniffing protection

  4. 4

    Exposing server and PHP version informationLow

    Why it matters: Disclosing server information can help attackers exploit known vulnerabilities.

    Fix: Remove or obfuscate the 'Server' and 'X-Powered-By' headers from responses.

    Evidence: Software version disclosure

  5. 5

    Missing Permissions-Policy headerInfo

    Why it matters: Not using a Permissions-Policy increases risks from potentially malicious scripts.

    Fix: Add the header: Permissions-Policy: geolocation=(self), microphone=(), camera=()

    Evidence: Permissions policy

What the checks found

  • FoundHTTP Strict Transport SecurityMedium

    No HTML page sends strict-transport-security. Without it a visitor who types the address without https:// can be intercepted on the first request.

    • https://alomran.info/ → no strict-transport-security
    • https://alomran.info/category/aboutalomran/ → no strict-transport-security
    • https://alomran.info/category/familytree/ → no strict-transport-security
    • https://alomran.info/category/alomranmanuscript/ → no strict-transport-security
    • https://alomran.info/category/cv/ → no strict-transport-security
    • https://alomran.info/category/albdareen/ → no strict-transport-security
    • https://alomran.info/category/aldawaser/ → no strict-transport-security
    • https://alomran.info/category/audatsudair/ → no strict-transport-security
    • https://alomran.info/category/audatsudairhistory/ → no strict-transport-security
    • https://alomran.info/category/emarhaudatsudair/ → no strict-transport-security
    • https://alomran.info/category/audatsudairsheikhs/ → no strict-transport-security
    • https://alomran.info/category/audatsudairpioneers/ → no strict-transport-security
  • FoundMIME sniffing protectionLow

    636 of 639 HTML pages send x-content-type-options. Without X-Content-Type-Options: nosniff a browser may run a file as a script because of its contents rather than its declared type.

    • https://alomran.info/wp-login.php?redirect_to=https%3A%2F%2Falomran.info%2Fwp-admin%2Fpost.php%3Fpost%3D499264%26action… → no x-content-type-options
    • https://alomran.info/wp-login.php?action=lostpassword → no x-content-type-options
    • https://alomran.info/wp-login.php → no x-content-type-options
  • FoundPermissions policyInfo

    636 of 639 HTML pages send permissions-policy. A Permissions-Policy header turns off browser features the site does not use (camera, microphone, geolocation), limiting what an injected script could do.

    • https://alomran.info/wp-login.php?redirect_to=https%3A%2F%2Falomran.info%2Fwp-admin%2Fpost.php%3Fpost%3D499264%26action… → no permissions-policy
    • https://alomran.info/wp-login.php?action=lostpassword → no permissions-policy
    • https://alomran.info/wp-login.php → no permissions-policy
  • FoundSoftware version disclosureLow

    Responses reveal the exact server or framework version, which lets an attacker look up known vulnerabilities for it without guessing.

    • server: hcdn (3202 responses)
    • x-powered-by: PHP/8.3.33 (651 responses)
  • FoundCookie flagsMedium

    9 of 10 cookies are missing protective flags. Without HttpOnly a script can read the cookie; without Secure it travels over plain HTTP; without SameSite it is sent on cross-site requests.

    • wordpress_test_cookie (set by https://alomran.info/wp-login.php?redirect_to=https%3A%2F%2Falomran.info%2Fwp-a…) lacks SameSite
    • wordpress_c677cf702280d5865474c6caebcaf65e (set by https://alomran.info/wp-login.php?redirect_to=https%3A%2F%2Falomran.info%2Fwp-a…) lacks HttpOnly, SameSite
    • wordpress_sec_c677cf702280d5865474c6caebcaf65e (set by https://alomran.info/wp-login.php?redirect_to=https%3A%2F%2Falomran.info%2Fwp-a…) lacks HttpOnly, SameSite
    • wordpress_logged_in_c677cf702280d5865474c6caebcaf65e (set by https://alomran.info/wp-login.php?redirect_to=https%3A%2F%2Falomran.info%2Fwp-a…) lacks HttpOnly, SameSite
    • wp-settings-0 (set by https://alomran.info/wp-login.php?redirect_to=https%3A%2F%2Falomran.info%2Fwp-a…) lacks HttpOnly, SameSite
    • wp-settings-time-0 (set by https://alomran.info/wp-login.php?redirect_to=https%3A%2F%2Falomran.info%2Fwp-a…) lacks HttpOnly, SameSite
    • wordpressuser_c677cf702280d5865474c6caebcaf65e (set by https://alomran.info/wp-login.php?redirect_to=https%3A%2F%2Falomran.info%2Fwp-a…) lacks HttpOnly, SameSite
    • wordpresspass_c677cf702280d5865474c6caebcaf65e (set by https://alomran.info/wp-login.php?redirect_to=https%3A%2F%2Falomran.info%2Fwp-a…) lacks HttpOnly, SameSite
    • wp-postpass_c677cf702280d5865474c6caebcaf65e (set by https://alomran.info/wp-login.php?redirect_to=https%3A%2F%2Falomran.info%2Fwp-a…) lacks HttpOnly, SameSite
11 checks passed
  • OKHTTPS

    All 639 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set.

  • OKClickjacking protection

    x-frame-options is set on all 639 HTML pages.

  • OKReferrer policy

    referrer-policy is set on all 639 HTML pages.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKForms over HTTPS

    81 forms found, all on HTTPS pages posting to HTTPS addresses.

  • OKVulnerable JavaScript libraries

    1 library version recognised, none with known vulnerabilities.

  • OKKeys and secrets in page code

    No API keys, tokens or private keys were found in the sampled HTML and scripts.

  • OKExposed files and listings

    None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.

  • OKThird-party scripts

    The sampled pages load no scripts from other domains.

  • OKSensitive paths in robots.txt

    robots.txt does not point at admin, backup or private paths.

A passive review of what the crawl recorded: response headers, page and script contents and the URLs it found. It does not probe the site, test TLS settings or look for files that were not linked. Generated automatically; verify each finding against your own site before acting on it.

Sites scoring near alomran.info

Their neighbours in the SEO rank table, which orders every scanned site by health score.

This report was produced by the DIY SEO Hub Site Spider crawling alomran.info from its pages as published, the way a search engine does. It shows summary figures only.

Own alomran.info?

alomran.info scan 2026-09-27-1154 | DIY SEO Hub