72cubes.com website review

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

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

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

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

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

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

About 91 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 460 ms faster on a phone.

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

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

3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 448 KiB and 136 ms of main-thread time.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 5.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Web Design & Content Marketing OUR WORK”. Most of its time is resource load delay (2.9 s).

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

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

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

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

1 image is downloaded at several times the size a phone draws it, for example 0e475bb9b17b3fa4f94f31fba1635b8f-telephone-call-icon-logo-by at 300 px wide, shown at 25 px. Resized copies would save about 49 KiB.

2 images (87 KiB) 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.

3 images further down the page (103 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 13 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.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 3 <h1> headlines (“Web Design”, “&” and “Content Marketing”). One clear main headline is easier for people and search engines.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://72cubes.com/sitemap.xml, so Google discovers your pages only by following links.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 18 pages on 72cubes.com and 0 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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.

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

/about-us, /services, /portfolio, /career, /contact-us and /feed have no meta description, so Google writes the search snippet from whatever text it finds.

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

/contact-us 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.

/about-us, /services, /portfolio and /career took over 3 s to send their HTML from our server.

We fetched 6 pages linked from your homepage and read each the way a search engine does.

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

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

10 resources load over plain http on your https page (for example http://72cubes.com/wp-content/uploads/2026/01/72Cubes-Logo-2.png); browsers block or warn about them.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

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.

72cubes.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.

72cubes.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.

Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

The homepage carries about 410 words of visible text.

72cubes.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

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