Website review, no card needed

foxfly.com.br logo

foxfly.com.br website review

Visit site (opens in a new tab)Reviewed 11 November 202633 issues · 73 checks

This review found 33 issues worth fixing on foxfly.com.br, 14 of them high impact, across 73 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 foxfly.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. foxfly.com.br at 0.4 s0.4 s
  2. foxfly.com.br at 0.8 s0.8 s
  3. foxfly.com.br at 1.2 s1.2 s
  4. foxfly.com.br at 1.6 s1.6 s
  5. foxfly.com.br at 2.1 s2.1 s
  6. foxfly.com.br at 2.5 s2.5 s
  7. foxfly.com.br at 2.9 s2.9 s
  8. foxfly.com.br at 3.3 s3.3 s

Speed

7 to fix66
  • Use efficient cache lifetimes

    1.6 s · 603 KiB

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

  • Render-blocking requests

    1.8 s

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

  • Improve image delivery

    900 ms · 187 KiB

    3 images could be 187 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

  • Mobile performance score: 66

    66/100

    Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    750 ms · 143 KiB

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

  • Font display

    650 ms

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

  • Reduce unused CSS

    300 ms · 58 KiB

    About 58 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Cloudflare and Google Fonts and others), adding 277 KiB and 165 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 10 KiB

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

  • 2 long tasks on the main thread

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

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.7 s

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

5 to fix67
  • Largest Contentful Paint: 8.9 s

    8.9 s

    Your largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Seu Parceiro Tecnológico Confiável Vamos Falar?”.

  • Time to Interactive: 9.0 s

    9.0 s

    The page becomes fully interactive after 9.0 s. Good is under 3.8 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.

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • 19 images without width and height

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

2 checks passed
  • Total Blocking Time: 89 ms

    89 ms

    Scripts block the page for only 89 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

1 to fix90
  • 1 image far larger than shown

    114 KiB

    1 image is downloaded at several times the size a phone draws it, for example LOGO-02.png at 2,000 px wide, shown at 191 px. Resized copies would save about 114 KiB.

  • 3 images in older formats

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

  • 1 image below the first screen load straight away

    1 image further down the page (78 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.4 g of CO₂ per visit

    0.41 g

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

1 checks passed
  • Page weight: 1.5 MB in 41 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 41 requests on a phone: images 812 KiB (13), scripts 365 KiB (11) and fonts 219 KiB (6). That is a lean page.

Accessibility

6 to fixGoogle 7685
  • Orphan list items

    Some list items are not inside a list.

  • 5 text elements with low contrast

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

  • Links must have discernible text (5 elements)

    Links must have discernible text: 5 elements on the page fail this check, rated serious by axe-core.

  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 8 buttons without a name

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 34 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 6 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 9271
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (16 characters)

    Your title is only 16 characters: “Home - foxfly IT”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 3 H1 headlines

    There are 3 <h1> headlines (“Seu parceiro”, “tecnológico” and “confiável”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, Organization, WebPage and WebSite) but with 1 problem, for example “Organization: missing name”.

  • No social preview image

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

  • 19 internal links, 1 external

    The homepage links to 19 pages on foxfly.com.br and 1 external page.

3 checks passed
  • Canonical URL set

    The canonical URL is https://new.foxfly.com.br/.

  • 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://new.foxfly.com.br/sitemaps.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing name, sameAs (social profiles) 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.

  • No llms.txt

    There is no https://new.foxfly.com.br/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 (377 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 3 pages without a meta description

    https://new.foxfly.com.br/blog, https://new.foxfly.com.br/contato and https://new.foxfly.com.br/enterprise-content-management-system-ecm have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://new.foxfly.com.br/blog, https://new.foxfly.com.br/cjm/canal-de-comunicacao-voce-sabe-a-preferencia-do-seu-cliente-2, https://new.foxfly.com.br/documentos-digitais/como-gerenciar-o-conteudo-empresarial and https://new.foxfly.com.br/gestao-de-ti/como-garantir-a-seguranca-dos-dados-na-sua-empresa have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://new.foxfly.com.br/contato has 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.

  • 6 internal pages checked

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

5 checks passed
  • Linked pages load

    All 6 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 6 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 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 409 ()”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

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

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

    The homepage carries about 376 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Analytics, HubSpot and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 7 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on foxfly.com.br, including 12 speed issues, 5 SEO issues and 4 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