digiquag.com website review

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

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

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

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

The HTML itself could arrive about 650 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 626 ms on a phone.

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

teepublic.com costs a phone 86 ms of main-thread work and 326 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.

Your server takes 726 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

3 third-party services load with your homepage (teepublic.com, Google Analytics and Cloudflare), adding 510 KiB and 203 ms of main-thread time.

1 long task block the main thread while loading, the longest for 51 ms. During a long task the page ignores taps.

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

12 KiB could be saved by minifying JavaScript.

10 KiB could be saved by minifying CSS.

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.

Your largest element takes 16.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “GARUDA404 | Jasa Web Design, Website Development, dan Solus…”.

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

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

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

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

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 2.9 MB in 29 requests on a phone: images 2.3 MB (13), scripts 326 KiB (9) and fonts 142 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 frame has no title, so screen-reader users cannot tell what it contains.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

1 element has a tabindex above 0, which scrambles the keyboard order.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 90 characters, so Google will cut it off around 60: “GARUDA404 | Jasa Web Design, Website Development, dan Solusi Digital Modern - digiquag.com”.

There are 2 <h1> headlines (“GARUDA404 | Jasa Web Design, Website Development,…” and “GARUDA404 | Jasa Web Design, Website Development,…”). One clear main headline is easier for people and search engines.

Your meta description is 386 characters; Google truncates after about 160, so the end of your pitch is cut.

No XML sitemap at http://digiquag.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at digiquag.com/robots.txt, the first file search crawlers ask for.

4 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 100 pages on digiquag.com and 11 external pages.

The robots meta tag says “index, follow, nosnippet”, which tells Google, Bing and the AI answers built on them not to quote this page.

There is no https://digiquag.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.

Your homepage links to https://digiquag.com/t-shirts/anime, https://digiquag.com/t-shirts/drinks, https://digiquag.com/t-shirts/fantasy, https://digiquag.com/t-shirts/food, https://digiquag.com/t-shirts/sci-fi and https://digiquag.com/t-shirts and 7 others, which answer with an error. Visitors hit a dead end and search engines drop them.

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

10 images failed to load on a phone, for example https://digiquag.com/myassetbannergaruda404.png.

6 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot set properties of null (setting 'innerHTML')”.

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

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

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

Before a visitor clicks anything, the page loads Google Analytics (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 3 cookies, 1 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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.