ffa.com.py website review

55 files are served with short cache lifetimes, so returning visitors download them again (1,000 KiB).

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

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

5 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and Cloudflare and others), adding 1.1 MB and 595 ms of main-thread time.

YouTube costs a phone 574 ms of main-thread work and 972 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.

About 527 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

Your largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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.

Your homepage downloads 2.5 MB in 168 requests on a phone: images 1.2 MB (15), scripts 1.0 MB (29) and stylesheets 116 KiB (22). Under 2 MB keeps phones on slow connections fast.

3 images (767 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.

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

5 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: 4 elements on the page fail this check, rated moderate by axe-core.

Banner landmark should not be contained in another landmark: 2 elements on the page fail this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 61 pages on ffa.com.py and 12 external pages.

Your Organization JSON-LD is missing url, 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.

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.

/inicio declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and /inicio all use the title “Início - Flavors and Fragrances of America S.A.”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/Downloads and /downloads use the same meta description. A description written for each page earns more clicks.

/inicio, /nosotros, /Downloads, /Contactos, /contactos and /separteffa and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR”.

Chrome logged issues while loading the page (“Mixed content”).

1 link from your homepage to your own site is broken, for example https://ffa.com.py/cdn-cgi/l/email-protection (404).

1 link to other sites is dead, for example https://www.linkedin.com/in/flavors-and-fragrances-of-am%C3%A9rica-2a551234/ (999).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

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

ffa.com.py 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.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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.

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

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 304 words of visible text.

ffa.com.py 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.

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

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

Opening the homepage sets 2 cookies, 1 of them by other companies (measured from a US location before any click).

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.

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