Website review, no card needed
adzitrims.com website review
Visit site (opens in a new tab)Reviewed 22 October 202635 issues · 79 checks
This review found 35 issues worth fixing on adzitrims.com, 17 of them high impact, across 79 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.7 s
1.4 s
2.2 s
2.9 s
3.6 s
4.3 s
5.0 s
5.8 s
Speed
Render-blocking requests
8.7 s46 files block the first paint until they finish downloading. Deferring or inlining them could save about 8.7 s.
Reduce unused CSS
4.5 s · 936 KiBAbout 936 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.5 s faster on a phone.
Reduce unused JavaScript
2.9 s · 548 KiBAbout 548 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.
Improve image delivery
350 ms · 932 KiB8 images could be 932 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 66). Pages that score under 90 lose visitors before the first paint.
Minify JavaScript
300 ms · 47 KiB47 KiB could be saved by minifying JavaScript.
Minify CSS
300 ms · 39 KiB39 KiB could be saved by minifying CSS.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 725 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
150 ms · 29 KiBPolyfills for old browsers add 29 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Document request latency
136 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 81 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
1 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 64 KiB and 0 ms of main-thread time.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 50 ms
50 msYour server sent the HTML in 50 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Real-user LCP: 7.4 s
7.4 sReal visitors wait 7.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 6.6 s
6.6 sReal visitors see the first content after 6.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.3 s
3.3 sReal visitors wait 3.3 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 11.6 s
11.6 sThe first text or image appears after 11.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 19.4 s
19.4 sYour largest element takes 19.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Adzi Trims Ltd. Commitment”.
Time to Interactive: 19.5 s
19.5 sThe page becomes fully interactive after 19.5 s. Good is under 3.8 s.
Speed Index: 12.7 s
12.7 sVisually, the page fills in at 12.7 s (Speed Index). Good is under 3.4 s.
4 checks passed
Real-user INP: 155 ms
155 msReal visitors wait 155 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 16 ms
16 msScripts block the page for only 16 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 5.3 MB in 130 requests
5.3 MBYour homepage downloads 5.3 MB in 130 requests on a phone: images 2.1 MB (20), scripts 1.4 MB (49) and stylesheets 1.1 MB (51). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
Adzi-Trims-won-the-1st-Prize-for-the-best-stall-of-GAPEXPO.p weighs 808 KiB. On a phone connection a single image that size takes seconds.
5 images in older formats
5 images (1,021 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.
About 1.5 g of CO₂ per visit
1.49 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.49 g of CO₂e: 179.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (29 elements)
All page content should be contained by landmarks: 29 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (15 characters)
Your title is only 15 characters: “Adzi Trims Ltd.”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
58 internal links, 8 external
The homepage links to 58 pages on adzitrims.com and 8 external pages.
4 checks passed
One H1 headline
Your main headline reads: “We deliver trims solutions trusted by global brands.”.
Canonical URL set
The canonical URL is https://www.adzitrims.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.adzitrims.com/wp-sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.adzitrims.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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (410 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://www.adzitrims.com/about-adzi-trims-ltd, https://www.adzitrims.com/mission-vision, https://www.adzitrims.com/our-awards, https://www.adzitrims.com/client-references, https://www.adzitrims.com/product-solutions and https://www.adzitrims.com/portfolio/woven-labels and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.adzitrims.com/about-adzi-trims-ltd, https://www.adzitrims.com/mission-vision, https://www.adzitrims.com/our-awards, https://www.adzitrims.com/client-references, https://www.adzitrims.com/product-solutions and https://www.adzitrims.com/portfolio/woven-labels and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
8 pages slow to respond
https://www.adzitrims.com/client-references, https://www.adzitrims.com/product-solutions, https://www.adzitrims.com/portfolio/woven-labels, https://www.adzitrims.com/portfolio/printed-fabric-labels-3, https://www.adzitrims.com/portfolio/adhesive-labels-tags and https://www.adzitrims.com/portfolio/woven-labels-4 and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 32 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://www.adzitrims.com/' was loaded over HTTPS, but requested an insecure stylesheet 'ht…”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
2 checks passed
Tap targets are thumb-sized
6 of 7 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 347 words of copy
The homepage carries about 347 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Get Quote”.
4 calls to action
The homepage has 4 calls to action, for example “Contact Us”, “Get Quote” and “Subscribe Sending”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo and 2 trust badges.
Privacy and tracking
No consent tool detected
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.
3 other companies contacted
Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at adzitrims.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- CMS
- WordPress
- Framework
- jQuery
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on adzitrims.com, including 16 speed issues, 4 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.