ahramsg.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user LCP: 3.6 s

  3.6 s

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

• Real-user FCP: 2.5 s

  2.5 s

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

• Real-user TTFB: 1.4 s

  1.4 s

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

• Largest content (LCP) held steady for real visitors

  -6%

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

• About 0.5 g of CO₂ per visit

  0.51 g

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

• 2 buttons without a name

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

  Elements (2)

• 10 text elements with low contrast

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

  Elements (3)

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

  All page content should be contained by landmarks: 31 elements on the page fail this check, rated moderate by axe-core.

  Elements (3)

• No main landmark

  The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  Elements (1)

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

  Elements (1)

• 6 form fields without a label

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

  View source

• 2 links without text

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

  Elements (2)

• 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 (2)

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

  Elements (2)

• Headings skip levels

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

  View sourceElements (3)

• No H1 headline

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

• Title is long (67 characters)

  Your title is 67 characters, so Google will cut it off around 60: “Ahram Security Group | Giving You the Power to Protect What Matters”.

  View source

• No structured data

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

• Meta description is long (161 characters)

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

  View source

• 37 internal links, 10 external

  The homepage links to 37 pages on ahramsg.com and 10 external pages.

• 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 pages with very little text

  /asg-catalogues and /project/blue-vert 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.

• 8 pages slow to respond

  /about-us, /asg-board-of-directors-members, /projects, /asg-catalogues, /afm and /sicuro and 2 others took over 3 s to send their HTML from our server.

• 15 internal pages checked

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

• 3 JavaScript errors while loading

  3 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 ()”.

• 2 broken links to your own pages

  2 links from your homepage to your own site are broken, for example https://ahramsg.com/project/al-alamein-towers/ (503).

• 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 Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• No security.txt

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

• No CAA record

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

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

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

• Local business without LocalBusiness data

  Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

• Thin social proof

  Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

• No opening hours

  The homepage shows no opening hours. If customers visit or call, show when.

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

  The homepage carries about 696 words of visible text.

• 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 trackers load before any consent

  3

  Before a visitor clicks anything, the page loads Google Ads, 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.

• 16 cookies set on arrival

  16

  Opening the homepage sets 16 cookies, 1 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.

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