frunco.com website review

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

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

The page has 3,800 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

22 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

7 third-party services load with your homepage (Shopify, nfcube.com and swymrelay.com and others), adding 2.5 MB and 784 ms of main-thread time.

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

Shopify costs a phone 762 ms of main-thread work and 1.2 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.

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

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

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

ecomsend.com costs a phone 0 ms of main-thread work and 1.2 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.

8 KiB could be saved by minifying JavaScript.

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

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

2 KiB could be saved by minifying CSS.

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

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

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

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

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

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

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

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

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 5.1 MB in 305 requests on a phone: images 2.7 MB (34), scripts 1.1 MB (101) and other files 951 KiB (127). Under 2 MB keeps phones on slow connections fast.

9c790a1ba80d91fb786d294ae22aa581.png weighs 1.2 MB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example 9c790a1ba80d91fb786d294ae22aa581.png at 1,080 px wide, shown at 177 px. Resized copies would save about 952 KiB.

1 image (1.2 MB) is 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.

Maison_de_frunco_-_1.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

ARIA toggle fields must have an accessible name: 74 elements on the page fail this check, rated serious by axe-core.

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

1 tap target is too small or too close together to hit reliably with a finger.

Document should not have more than one banner landmark: 1 element on the page fails 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.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is only 21 characters: “frunco official store”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 48 characters: “frunco official storeは、frunco(フランコ)の「公式通販サイト」です。”. 70 to 160 characters is enough to sell the click.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 148 pages on frunco.com and 13 external pages.

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

/customer_authentication/redirect has no <title>, so Google invents the link text in results.

/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/collections/all, /customer_authentication/redirect, /collections/ranking and /policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/outer/%E3%82%B8%E3%83%A3%E3%82%B1%E3%83%83%E3%83%88 and /collections/outer/%E3%82%B3%E3%83%BC%E3%83%88 use the same meta description. A description written for each page earns more clicks.

Your homepage links to 7 pages by a URL that isn't their canonical one, for example /pages/frunco-membership-%E3%83%9D%E3%82%A4%E3%83%B3%E3%83%88%E5%88%B6%E5%BA%A6%E3%82%B9%E3%82%BF%E3%83%BC%E3%83%88%E3%81%AE%E3%81%8A%E7%9F%A5%E3%82%89%E3%81%9B, whose canonical is /pages/frunco-membership-%e3%83%9d%e3%82%a4%e3%83%b3%e3%83%88%e5%88%b6%e5%ba%a6%e3%82%b9%e3%82%bf%e3%83%bc%e3%83%88%e3%81%ae%e3%81%8a%e7%9f%a5%e3%82%89%e3%81%9b. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

/policies/shipping-policy and /pages/frunco-membership-%E3%83%9D%E3%82%A4%E3%83%B3%E3%83%88%E5%88%B6%E5%BA%A6%E3%82%B9%E3%82%BF%E3%83%BC%E3%83%88%E3%81%AE%E3%81%8A%E7%9F%A5%E3%82%89%E3%81%9B have 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.

/customer_authentication/redirect, /collections/tops/T%E3%82%B7%E3%83%A3%E3%83%84%E3%83%BB%E3%82%AB%E3%83%83%E3%83%88%E3%82%BD%E3%83%BC%E3%83%BB%E3%83%88%E3%83%AC%E3%83%BC%E3%83%8A%E3%83%BC and /collections/tops/%E3%83%8B%E3%83%83%E3%83%88%E3%83%BB%E3%82%BB%E3%83%BC%E3%82%BF%E3%83%BC%E3%83%BB%E3%82%AB%E3%83%BC%E3%83%87%E3%82%A3%E3%82%AC%E3%83%B3 took over 3 s to send their HTML from our server.

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

13 of 45 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 “Failed to load resource: the server responded with a status of 404 ()”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://www.frunco.com/customer_authentication/redirect?locale=ja&region_country=JP.

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.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

frunco.com'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.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage has only about 246 words of visible text; thin pages give Google and first-time buyers little to go on.

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

DMARC is set to p=none, so mail pretending to be frunco.com is still delivered. Add a report address, check the reports, then move to quarantine.

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, Google Tag Manager, Meta Pixel and Pinterest Tag (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 16 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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.