tractafrictae.com website review

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.1 s faster on a phone.

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

Google CDN costs a phone 1.3 s of main-thread work and 1.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Google CDN, ShareThis and Google Tag Manager and others), adding 3.3 MB and 2.2 s of main-thread time.

ShareThis costs a phone 428 ms of main-thread work and 719 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.

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

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

Google Tag Manager costs a phone 291 ms of main-thread work and 312 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.

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

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

15 KiB could be saved by minifying JavaScript.

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

Desktop scores 43 but mobile only 10. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

6 KiB could be saved by minifying CSS.

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.

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.

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

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

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

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

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

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

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

The layout shifts by 0.454 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

Your homepage downloads 6.7 MB in 142 requests on a phone: scripts 2.8 MB (34), images 2.6 MB (59) and other files 830 KiB (26). Under 2 MB keeps phones on slow connections fast.

10 images (1.3 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.

5 images further down the page (849 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example 64e0f5944c6db.jpg at 1,920 px wide, shown at 340 px. Resized copies would save about 137 KiB.

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

8 dropdowns have no label.

Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

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

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

All page content should be contained by landmarks: 44 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: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Alternative text of images should not be repeated as text: 21 elements on the page fail this check, rated minor by axe-core.

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

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

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

Your title is 75 characters, so Google will cut it off around 60: “Tractafric Equipment | No. 1 in equipment in Morocco and Sub-Saharan Africa”.

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

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

No XML sitemap at https://www.tractafric-equipment.com/sitemap.xml, so Google discovers your pages only by following links.

17 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Your hreflang tags are invalid, so Google may show the wrong language version.

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

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

The homepage links to 202 pages on tractafrictae.com and 10 external pages.

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.

There is no https://www.tractafric-equipment.com/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.tractafric-equipment.com/en, https://www.tractafric-equipment.com/en/en/tractafric-equipment.html, https://www.tractafric-equipment.com/en/en/compliance.html, https://www.tractafric-equipment.com/en/en/latest-news.html, https://www.tractafric-equipment.com/en/en/industries-and-sectors.html and https://www.tractafric-equipment.com/en/en/best-value.html and 10 others all use the title “Tractafric Equipment | No. 1 in equipment in Morocco and Sub-Saharan …”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.tractafric-equipment.com/en/en/tractafric-equipment.html, https://www.tractafric-equipment.com/en/en/compliance.html, https://www.tractafric-equipment.com/en/en/latest-news.html, https://www.tractafric-equipment.com/en/en/industries-and-sectors.html, https://www.tractafric-equipment.com/en/en/best-value.html and https://www.tractafric-equipment.com/en/en/network.html and 9 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 15 pages by a URL that isn't their canonical one, for example https://www.tractafric-equipment.com/en/en/tractafric-equipment.html, whose canonical is https://www.tractafric-equipment.com/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.tractafric-equipment.com/en/en/tractafric-equipment.html, https://www.tractafric-equipment.com/en/en/compliance.html, https://www.tractafric-equipment.com/en/en/latest-news.html, https://www.tractafric-equipment.com/en/en/industries-and-sectors.html, https://www.tractafric-equipment.com/en/en/best-value.html and https://www.tractafric-equipment.com/en/en/network.html and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 104 found) and read each the way a search engine does.

4 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://data.stbuttons.click/data' from origin 'https://www.tractafric-equipment.com' has …”.

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

Your longest form asks for 14 fields (4 required). Every extra field lowers completion.

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

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and The Trade Desk (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 5 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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.