afaqsec.com website review

• Google's speed test didn't respond

  Google's speed test didn't respond for this site, so speed and Core Web Vitals are not measured here. Your full playbook measures them.

Not measured in this review.

• Page weight: 4.1 MB

  4.1 MB

  Your homepage downloads 4.1 MB on a phone, 2.7 MB of it images (67%). Under 2 MB keeps phones on slow connections fast.

• 1 image over 500 KB

  Untitled-1.png weighs 539 KiB. On a phone connection a single image that size takes seconds.

  Elements (1)

• 3 images in older formats

  3 images (803 KiB) 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.

  Elements (3)

• 3 images below the first screen load straight away

  3 images further down the page (803 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (3)

• About 1.1 g of CO₂ per visit

  1.15 g

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

• 38 buttons without a name

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

  Elements (3)

• ARIA attributes must conform to valid values (1 element)

  ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  Elements (1)

• 1 text element with low contrast

  1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  Elements (1)

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

  Elements (2)

• Zoom is disabled

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

  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)

• 11 links without text

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

  Elements (3)

• 1 form field without a label

  1 form field has no label, so screen readers announce an empty box and autofill guesses.

  View source

• Headings skip levels

  Headings skip levels (h3 → h6, h2 → h6 and h2 → h5), 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.

• 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

• 311 internal links, 35 external

  The homepage links to 311 pages on afaqsec.com and 35 external pages.

• Organization data is thin (2 of 6 facts)

  Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  View source

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

• 13 pages without an H1

  /it-services, /infra-structure-network, /central, /ip-telephone, /digital-telephone and /visual-system and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

• 10 pages slow to respond

  /digital-telephone, /visual-system, /audio, /video, /fire-alarm and /cloud-service and 4 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 77 found) and read each the way a search engine does.

• 18 small tap targets

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

• Scrolls sideways on phones

  On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

• 4 broken external links

  4 links to other sites are dead, for example https://www.twitter.com/afaqsecurity/ (404).

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

• 1 link through redirect chains

  1 link go through two or more redirects, for example https://1.envato.market/5Q25j.

• 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

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

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

• No social proof

  No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  View source

• Phone number is not tap-to-call

  Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

• No map or directions link

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

• 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 1,948 words of copy

  The homepage carries about 1,948 words of visible text.

• No DMARC policy

  afaqsec.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

• No DKIM key on the usual selectors

  We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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

• 16 other companies contacted

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