Website review, no card needed

amiviz.com logo

amiviz.com website review

Visit site (opens in a new tab)Reviewed 20 October 202646 issues · 87 checks

This review found 46 issues worth fixing on amiviz.com, 17 of them high impact, across 87 checks. The most urgent: render-blocking requests. 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
5.3 s3.1 sMay 23Oct 175.0 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.3 s
May 30, 20264.3 s
Jul 25, 20263.8 s
Aug 1, 20263.8 s
Aug 8, 20263.5 s
Aug 15, 20263.6 s
Aug 22, 20264.0 s
Aug 29, 20264.0 s
Sep 5, 20264.2 s
Sep 12, 20264.4 s
Sep 19, 20264.2 s
Sep 26, 20264.7 s
Oct 3, 20265.0 s
Oct 10, 20265.1 s
Oct 17, 20265.0 s
Real-visitor tap response (INP)75th percentile, phones
86 ms70 msAug 8Oct 1777 ms
Show as table
DateReal-visitor tap response (INP)
Aug 8, 202675 ms
Aug 15, 202672 ms
Aug 22, 202679 ms
Aug 29, 202679 ms
Sep 5, 202679 ms
Sep 19, 202679 ms
Sep 26, 202684 ms
Oct 3, 202678 ms
Oct 10, 202679 ms
Oct 17, 202677 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 amiviz.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. amiviz.com at 1.0 s1.0 s
  2. amiviz.com at 2.1 s2.1 s
  3. amiviz.com at 3.1 s3.1 s
  4. amiviz.com at 4.1 s4.1 s
  5. amiviz.com at 5.1 s5.1 s
  6. amiviz.com at 6.2 s6.2 s
  7. amiviz.com at 7.2 s7.2 s
  8. amiviz.com at 8.2 s8.2 s

Speed

14 to fix20
  • Render-blocking requests

    2.7 s

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

  • Reduce unused CSS

    1.2 s · 153 KiB

    About 153 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • 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: 20

    20/100

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

  • Reduce unused JavaScript

    160 ms · 809 KiB

    About 809 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 160 ms faster on a phone.

  • Reduce initial server response time

    952 ms

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

  • Document request latency

    950 ms

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

  • Improve image delivery

    565 KiB

    11 images could be 565 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 7 long tasks on the main thread

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

  • Use efficient cache lifetimes

    385 KiB

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

  • Google Tag Manager adds 344 ms

    344 ms

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

  • Main-thread work: 2.5 s

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

  • Google CDN adds 147 ms

    147 ms

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

  • Server response: 1.1 s

    1.1 s

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Google CDN and Other Google APIs/SDKs and others), adding 733 KiB and 493 ms of main-thread time.

  • Minify CSS

    160 ms · 13 KiB

    13 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    20 KiB

    Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

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

Core Web Vitals

13 to fix33
  • 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.

  • Real-user LCP: 4.3 s

    4.3 s

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

  • Real-user CLS: 1.17

    1.17

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

  • Real-user FCP: 4.1 s

    4.1 s

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

  • Real-user TTFB: 2.8 s

    2.8 s

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

  • Speed Index: 15.9 s

    15.9 s

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

  • First Contentful Paint: 6.8 s

    6.8 s

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

  • Largest Contentful Paint: 7.9 s

    7.9 s

    Your largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (3.9 s).

  • Time to Interactive: 17.8 s

    17.8 s

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

  • Cumulative Layout Shift: 0.694

    0.694

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

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

    +33%

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

  • Total Blocking Time: 513 ms

    513 ms

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

  • 7 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +6%

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

1 checks passed
  • Real-user INP: 76 ms

    76 ms

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

Images and page weight

3 to fix69
  • Page weight: 3.4 MB in 124 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 124 requests on a phone: scripts 1.4 MB (9), images 1.0 MB (105) and HTML 691 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    no-image.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 2 images in older formats

    2 images (520 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.

  • About 1.0 g of CO₂ per visit

    0.96 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.96 g of CO₂e: 115.4 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

4 to fixGoogle 8393
  • 8 buttons without a name

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

  • 28 images without alt text

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

  • 4 links without text

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

  • 1 form field without a label

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

  • Headings skip levels

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

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 8589
  • 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 (316 characters)

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

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 38 internal links, 2 external

    The homepage links to 38 pages on amiviz.com and 2 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “AmiViz is a leading cybersecurity-focused value-added distributor headquartered in the Middle East”.

  • Title: 30 characters

    Your title is a healthy 30 characters: “AmiViz: Enterprise Marketplace”.

  • Canonical URL set

    The canonical URL is https://www.amiviz.com/home.

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

AI search readiness

1 to fix88
  • 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.amiviz.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.

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

  • Text is in the HTML

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

Other pages

4 to fix81
  • 6 pages share 2 titles

    https://www.amiviz.com/findreseller, https://www.amiviz.com/demorequest and https://www.amiviz.com/quoterequest all use the title “Login Required Page | AmiViz”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://www.amiviz.com/findreseller, https://www.amiviz.com/demorequest, https://www.amiviz.com/quoterequest, https://www.amiviz.com/contact_us, https://www.amiviz.com/contactus and https://www.amiviz.com/promotion_offer have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://www.amiviz.com/read_full_news/90, https://www.amiviz.com/read_full_news/89 and https://www.amiviz.com/read_full_news/88 use the same meta description. A description written for each page earns more clicks.

  • 13 pages without an H1

    https://www.amiviz.com/findreseller, https://www.amiviz.com/solutions, https://www.amiviz.com/services, https://www.amiviz.com/vendors, https://www.amiviz.com/demorequest and https://www.amiviz.com/quoterequest and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages with very little text

    https://www.amiviz.com/findreseller, https://www.amiviz.com/solutions, https://www.amiviz.com/services, https://www.amiviz.com/vendors, https://www.amiviz.com/demorequest and https://www.amiviz.com/quoterequest and 3 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.

  • 1 page slow to respond

    https://www.amiviz.com/services took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 2 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 16 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

4 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Request For Demo”, “Request For Quote” and “Contact Us”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Umami.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 5 cookies set on arrival

    5

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

  • 6 other companies contacted

    Loading the homepage contacts 6 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 amiviz.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Odoo
Framework
Tailwind CSS
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on amiviz.com, including 27 speed issues, 3 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