Website review, no card needed

aeffeonline.it logo

aeffeonline.it website review

Visit site (opens in a new tab)Reviewed 17 November 202640 issues · 75 checks

This review found 40 issues worth fixing on aeffeonline.it, 20 of them high impact, across 75 checks. The most urgent: use efficient cache lifetimes. 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

Full-page screenshot of aeffeonline.it (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aeffeonline.it at 1.1 s1.1 s
  2. aeffeonline.it at 2.2 s2.2 s
  3. aeffeonline.it at 3.4 s3.4 s
  4. aeffeonline.it at 4.5 s4.5 s
  5. aeffeonline.it at 5.6 s5.6 s
  6. aeffeonline.it at 6.7 s6.7 s
  7. aeffeonline.it at 7.8 s7.8 s
  8. aeffeonline.it at 9.0 s9.0 s

Speed

12 to fix46
  • Use efficient cache lifetimes

    10.1 s · 4.1 MB

    36 files are served with short cache lifetimes, so returning visitors download them again (4.1 MB).

  • Improve image delivery

    2.5 s · 2.5 MB

    10 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.

  • Render-blocking requests

    3.5 s

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

  • Reduce unused JavaScript

    2.6 s · 511 KiB

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

  • Reduce unused CSS

    1.5 s · 325 KiB

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

  • Mobile performance score: 46

    46/100

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

  • Main-thread work: 7.9 s

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

  • Font display

    900 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 900 ms).

  • 10 long tasks on the main thread

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

  • Legacy JavaScript

    400 ms · 50 KiB

    Polyfills for old browsers add 50 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

  • Minify CSS

    300 ms · 49 KiB

    49 KiB could be saved by minifying CSS.

  • Minify JavaScript

    300 ms · 47 KiB

    47 KiB could be saved by minifying JavaScript.

  • 6 third-party services on the page

    6 third-party services load with your homepage (iubenda, Cloudflare CDN and acswapp.com and others), adding 777 KiB and 377 ms of main-thread time.

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

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

6 to fix53
  • Largest Contentful Paint: 18.4 s

    18.4 s

    Your largest element takes 18.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Noi (www.aeffeonline.it/) e terze parti selezionate (6) rac…”.

  • Time to Interactive: 18.7 s

    18.7 s

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

  • Speed Index: 10.2 s

    10.2 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Total Blocking Time: 491 ms

    491 ms

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

  • 12 images without width and height

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

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

1 checks passed
  • Cumulative Layout Shift: 0.013

    0.013

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

Images and page weight

5 to fix18
  • Page weight: 4.7 MB in 60 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 60 requests on a phone: images 2.8 MB (14), scripts 1.3 MB (27) and stylesheets 328 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    nastrohome2.png weighs 1.5 MB. On a phone connection a single image that size takes seconds.

  • 8 images far larger than shown

    1.5 MB

    8 images are downloaded at several times the size a phone draws them, for example nastrohome2.png at 1,920 px wide, shown at 390 px. Resized copies would save about 1.5 MB.

  • 8 images in older formats

    8 images (2.7 MB) 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.

  • 8 images below the first screen load straight away

    8 images further down the page (2.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.3 g of CO₂ per visit

    1.33 g

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

Accessibility

4 to fixGoogle 8794
  • 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.

  • 2 images without alt text

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

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

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

  • 2 links without text

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

  • Headings skip levels

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

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

6 to fixGoogle 8274
  • No H1 headline

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

  • No structured data

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

  • No canonical URL

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No robots.txt

    There is no robots.txt at aeffeonline.it/robots.txt, the first file search crawlers ask for.

  • 3 links crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 14 internal links, 5 external

    The homepage links to 14 pages on aeffeonline.it and 5 external pages.

3 checks passed
  • Meta description: 119 characters

    Your meta description is 119 characters: “Production of woven and jacquard tapes, pipings, knitted tapes, elastic cords and drawstrings for clothing and footwear”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “Craftsmanship wearing creativity - AEFFE S.r.l.”.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.aeffeonline.it/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.aeffeonline.it/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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

2 to fix90
  • 12 pages without a meta description

    https://www.aeffeonline.it/essenza, https://www.aeffeonline.it/produzione, https://www.aeffeonline.it/produzione/fettucce-cordoni-coulisse, https://www.aeffeonline.it/produzione/bande-maglia, https://www.aeffeonline.it/produzione/nastri-moda and https://www.aeffeonline.it/produzione/piping-moda and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://www.aeffeonline.it/essenza, https://www.aeffeonline.it/produzione, https://www.aeffeonline.it/produzione/fettucce-cordoni-coulisse, https://www.aeffeonline.it/produzione/bande-maglia, https://www.aeffeonline.it/produzione/nastri-moda and https://www.aeffeonline.it/produzione/piping-moda and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://www.aeffeonline.it/produzione/bande-maglia, https://www.aeffeonline.it/produzione/nastri-moda, https://www.aeffeonline.it/produzione/piping-moda, https://www.aeffeonline.it/produzione/nastri-coulisse-elastiche and https://www.aeffeonline.it/approfondimenti 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.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 12 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix40
  • 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 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 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 313 words of copy

    The homepage carries about 313 words of visible text.

2 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies (measured from a US location before any click).

  • 9 other companies contacted

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

1 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) loads with the page.

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 aeffeonline.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics
Hosting
SEEWEB s.r.l.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on aeffeonline.it, including 18 speed issues, 6 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