fgi.org website review

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

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

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

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

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

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 2.1 MB and 762 ms of main-thread time.

Google CDN costs a phone 556 ms of main-thread work and 1.5 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.

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

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

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

Polyfills for old browsers add 29 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.

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 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Your largest element takes 27.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WELCOME Fashion Group International We are a worldwide memb…”.

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

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

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

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

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

Your homepage downloads 6.3 MB in 83 requests on a phone: images 2.8 MB (23), scripts 1.8 MB (23) and other files 707 KiB (7). Under 2 MB keeps phones on slow connections fast.

5 images (734 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.

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

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

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

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

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

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

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

Elements marked as presentational should be consistently ignored: 6 elements on the page fail this check, rated minor by axe-core.

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

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

There are 2 <h1> headlines (“WELCOME” and “WELCOME”). One clear main headline is easier for people and search engines.

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

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 157 pages on fgi.org and 4 external pages.

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.

/articles, /articles/filter_by/press and /articles/filter_by/fgi-communique all use the title “ARTICLES - Fashion Group International”. Search engines can't tell which page to show for a search, so each competes with the others.

/about, /about/foundation, /about/archives, /events, /articles and /articles/filter_by/press and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

/fgi-communique-2025-september, /fgi-communique-2025-february, /fgi-communique-2024-september, /fgi-communique-2024-february, /fgi-communique-2023-september and /fgi-communique-2023 use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /articles/filter_by/press, whose canonical is /articles. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/fgi-communique-2025-february took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://fgi.avantelogic.com/wp-content/uploads/2023/01/Maryanne-Signature.png.

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

1 error was logged to the browser console while the page loaded, for example “jQuery is not defined”.

1 image is served at too low a resolution for sharp phone screens.

Large scripts ship without source maps.

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

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

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

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

fgi.org 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.

fgi.org's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

fgi.org 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 Analytics and Google Tag Manager (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 (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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.