Programmable

Website review, no card needed

amicissolutions.com logo

amicissolutions.com website review

Visit site (opens in a new tab)Reviewed 21 October 202623 issues · 73 checks

This review found 23 issues worth fixing on amicissolutions.com, 10 of them high impact, across 73 checks. The most urgent: reduce unused JavaScript. 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

Site score

78C

Closest competitors among reviewed websites

Compare side by side

One score from every part of this review. How it works

amicissolutions.com (opens in a new tab)
Live view · interaction off

Speed

3 to fix72

  • Reduce unused JavaScript

    1.4 s · 335 KiB

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

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 72

    72/100

    Your mobile performance score is 72 (desktop: 71). Pages that score under 90 lose visitors before the first paint.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics and others), adding 192 KiB and 137 ms of main-thread time.

  • 4 long tasks on the main thread

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

  • Improve image delivery

    18 KiB

    1 image could be 18 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    17 KiB

    About 17 KiB of CSS is downloaded but never applied on this page.

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

2 checks passed

  • Main-thread work: 0.9 s

    A phone's processor spends 0.9 s on main-thread work while loading, 336 ms of it running JavaScript. That is comfortably low.

  • Server response: 7 ms

    7 ms

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

Core Web Vitals

4 to fix74

  • Largest Contentful Paint: 5.2 s

    5.2 s

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

  • Speed Index: 6.1 s

    6.1 s

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

  • Time to Interactive: 5.9 s

    5.9 s

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

  • First Contentful Paint: 2.5 s

    2.5 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed

  • Total Blocking Time: 80 ms

    80 ms

    Scripts block the page for only 80 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.004

    0.004

    The layout barely moves while loading (CLS 0.004, good is under 0.1).

Images and page weight

100

  • About 0.4 g of CO₂ per visit

    0.37 g

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

4 checks passed

  • Page weight: 1.3 MB in 31 requests

    1.3 MB

    Your homepage downloads 1.3 MB in 31 requests on a phone: images 722 KiB (20), scripts 572 KiB (2) and stylesheets 24 KiB (4). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

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

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 17 text elements with low contrast

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

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

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

1 checks passed

  • 37 automated accessibility rules passed

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

SEO

5 to fixGoogle 10072

  • No H1 headline

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

  • Title is long (77 characters)

    Your title is 77 characters, so Google will cut it off around 60: “Amicis Solutions | Transformative Commerce Solutions Built on Microsoft Cloud”.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (205 characters)

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

4 checks passed

  • Structured data in place

    Structured data found: Organization.

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

AI search readiness

1 to fix75

  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 944 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • llms.txt published

    The site publishes /llms.txt (3 KiB, 0 links), a plain-text guide to the site for AI tools.

Best practices

Google 100100

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed

  • No console errors

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

  • Tap targets are thumb-sized

    6 of 6 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

1 to fix92

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

5 checks passed

  • Served over HTTPS

    The homepage is served over HTTPS (amicissolutions.com).

  • Valid certificate (55 days left)

    The certificate from Let's Encrypt · YE1 verifies for amicissolutions.com and is valid for another 55 days.

  • HSTS enabled

    Strict-Transport-Security is set, so browsers always use https.

  • http:// redirects to https

    http://amicissolutions.com redirects to the secure version.

  • HTTP/2

    The server speaks HTTP/2, so browsers load many files over one connection.

Domain and trust

4 checks passed

  • Domain is 8 years old

    8 years

    amicissolutions.com was registered in Jan 2018 through Squarespace Domains II LLC. An established domain carries more trust with email providers and search engines.

  • Certificate issuers are restricted

    CAA records allow only letsencrypt.org to issue certificates for amicissolutions.com, so a mis-issued certificate from anyone else is refused.

  • DNSSEC is on

    amicissolutions.com's DNS answers are signed (DNSSEC), so they can't be forged on the way to visitors.

  • Registered until Jan 2027

    amicissolutions.com is registered until Jan 2027.

Content and conversion

3 to fix50

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 944 words of visible text.

2 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Sales”.

  • Analytics in place

    Analytics detected: Google Analytics.

Email authentication

1 to fix75

  • DMARC is monitor-only (p=none)

    DMARC is set to p=none, so mail pretending to be amicissolutions.com is still delivered. Add a report address, check the reports, then move to quarantine.

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

2 checks passed

  • SPF with a strict ending (-all)

    An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 include:spf.protection.outlook.com -all”.

  • DKIM signing found

    A DKIM key is published (selector “selector1”), so receivers can verify mail really came from you.

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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 5 other companies contacted

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

Upkeep, stack and company

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This free review found 23 issues on amicissolutions.com, including 7 speed issues, 5 SEO issues and 3 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