dogelthy.com website review

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

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

66 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Shopify, Google Tag Manager and figpii.com and others), adding 1.6 MB and 1.2 s of main-thread time.

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

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

About 819 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

13 KiB could be saved by minifying JavaScript.

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

4 KiB could be saved by minifying CSS.

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.

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

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

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

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

Real visitors wait 309 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

Your homepage downloads 9.1 MB in 451 requests on a phone: images 4.2 MB (135), scripts 1.7 MB (82) and media 1.6 MB (1). Under 2 MB keeps phones on slow connections fast.

14 images (1.5 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 (461 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images are downloaded at several times the size a phone draws them, for example DOG3V2.webp at 700 px wide, shown at 72 px. Resized copies would save about 144 KiB.

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

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

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

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

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

25 images have no alt text, which hurts accessibility and image search.

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

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

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

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

The homepage links to 199 pages on dogelthy.com and 9 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.

robots.txt blocks GPTBot and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

/collections/todos-los-productos, /collections/gastro and /collections/relajacion have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

Requests the notification permission on page load.

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.dogelthy.com/customer_authentication/redirect?locale=es&region_country=MX.

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.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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 3,631 words of visible text.

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

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 Ads, Google Tag Manager, Klaviyo, Microsoft Clarity and Pinterest Tag and 2 mores (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 28 cookies, 5 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 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.