designity.com website review

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

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

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

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

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

8 third-party services load with your homepage (website-files.com, Facebook and TikTok and others), adding 1.4 MB and 2.0 s of main-thread time.

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

website-files.com costs a phone 729 ms of main-thread work and 652 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 115 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

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

TikTok costs a phone 254 ms of main-thread work and 173 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.

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

Polyfills for old browsers add 47 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

Desktop scores 66 but mobile only 31. 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.

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.

Your largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “You shouldn’t have to choose between burnout or broken crea…”.

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

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

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

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

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

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

2 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-17, real Chrome visitors' tap response (inp) went from 270 ms to 271 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.5 MB in 179 requests on a phone: scripts 1.9 MB (76), images 198 KiB (37) and stylesheets 132 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 element hidden from screen readers can still receive keyboard focus.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

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

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

The homepage links to 159 pages on designity.com and 14 external pages.

/demo has 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.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97261108&tm=gtm002&Ver=2&mid=ab7825c3-4f27-45aa-a199-acdd5755c656&bo=1&sid=57a7ada0cf2811f19ed697b55fe861ab&vid=57a7d3d0cf2811f1af041543ca365ef4&vids=1&msclkid=N&gtm_t.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CERT_AUTHORITY_INVALID”.

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

Large scripts ship without source maps.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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.

designity.com is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

designity.com 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.

designity.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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 5,404 words of visible text.

DMARC is set to p=none, so mail pretending to be designity.com is still delivered. Reports are on, so moving to quarantine is the next step.

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 Ads, Google Tag Manager, HubSpot, LinkedIn Insight and Meta Pixel and 5 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 20 cookies (measured from a US location before any click).

Loading the homepage contacts 41 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.