shippify.com.br website review

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

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

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

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

34 images could be 8.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (jelou.ai, shippify.co and FontAwesome CDN and others), adding 17.3 MB and 720 ms of main-thread time.

shippify.co costs a phone 271 ms of main-thread work and 15.9 MB 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 760 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

jelou.ai costs a phone 319 ms of main-thread work and 811 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.

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

FontAwesome CDN costs a phone 81 ms of main-thread work and 490 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.

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

6 KiB could be saved by minifying JavaScript.

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.

5 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 11.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A empresa de logística com a tecnologia mais avançada do me…”.

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 17.6 MB in 107 requests on a phone: images 14.8 MB (67), scripts 2.4 MB (17) and fonts 232 KiB (7). Under 2 MB keeps phones on slow connections fast.

22 images (2.9 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.

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

4 images are downloaded at several times the size a phone draws them, for example feat-01-routing.png at 1,269 px wide, shown at 390 px. Resized copies would save about 150 KiB.

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

2 dropdowns have no label.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

Your canonical URL points to shippify.co, not shippify.com.br, so Google may credit that host instead.

There are 3 <h1> headlines (“A empresa de logística com a tecnologia mais avan…”, “Nosso sistema se conecta aonde for preciso” and “Se cadastre para realizar entregas pela Shippify.”). One clear main headline is easier for people and search engines.

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

Structured data found (BreadcrumbList and Organization) but with 1 problem, for example “Organization: url points at a different host (https://www.shippify.co)”.

The homepage links to 7 pages on shippify.com.br and 15 external pages.

There is no https://www.shippify.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.

https://www.shippify.com.br/privacy and https://www.shippify.com.br/terms/pt have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.shippify.com.br/companies, https://www.shippify.com.br/privacy, https://www.shippify.com.br/shippers and https://www.shippify.com.br/terms/pt have no <h1> headline, so visitors and search engines get no clear main topic.

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

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 ()”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 594 words of visible text.

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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.