wedefy.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Vimeo and others), adding 2.6 MB and 1.6 s of main-thread time.

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

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

Vimeo costs a phone 262 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.

Facebook costs a phone 302 ms of main-thread work and 221 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.

About 13 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.

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

Polyfills for old browsers add 56 KiB JavaScript that modern phones do not need. 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 206 ms. During a long task the page ignores taps.

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

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

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.

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

Your largest element takes 15.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FEATURED WORK”.

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

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

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

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 50.9 MB in 97 requests on a phone: media 45.9 MB (9), scripts 2.6 MB (38) and images 1.9 MB (13). Under 2 MB keeps phones on slow connections fast.

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

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

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

Structured data found (BreadcrumbList, Organization, WebPage and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://wedefy.wpengine.com/)”.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 82 pages on wedefy.com and 11 external pages.

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

There is no https://wedefy.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://wedefy.com/projects/vicinity-brand-video and https://wedefy.com/projects/elior-north-america-dining-events have no meta description, so Google writes the search snippet from whatever text it finds.

https://wedefy.com/about and https://wedefy.com/contact have no <h1> headline, so visitors and search engines get no clear main topic.

https://wedefy.com/contact and https://wedefy.com/projects/nike-docuseries-work-in-progress took over 3 s to send their HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

The homepage has only about 77 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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (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 9 cookies, 2 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 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.