Website review, no card needed
pazinoecc.com website review
Visit site (opens in a new tab)Reviewed 25 October 202634 issues · 76 checks
This review found 34 issues worth fixing on pazinoecc.com, 16 of them high impact, across 76 checks. The most urgent: use efficient cache lifetimes. 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
69D- #101,131 of 117,615 reviewed websitesbeats 12%
- #61,456 of 66,923 online storesbeats 7%
- #2,186 of 2,700 WooCommerce storesbeats 16%
Closest competitors among WooCommerce stores
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
4.0 s · 859 KiB218 files are served with short cache lifetimes, so returning visitors download them again (859 KiB).
Render-blocking requests
4.5 s87 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.5 s.
Reduce unused JavaScript
3.2 s · 578 KiBAbout 578 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.2 s faster on a phone.
Reduce unused CSS
1.8 s · 391 KiBAbout 391 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Improve image delivery
1.1 s · 687 KiB4 images could be 687 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 37
37/100Your mobile performance score is 37 (desktop: 10). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.5 s
A phone's processor spends 8.5 s on main-thread work while loading, 3.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6 third-party services on the page
6 third-party services load with your homepage (YouTube, WordPress Site Stats and Cloudflare and others), adding 1.3 MB and 854 ms of main-thread time.
YouTube adds 784 ms
784 msYouTube costs a phone 784 ms of main-thread work and 979 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.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 317 ms. During a long task the page ignores taps.
Minify JavaScript
300 ms · 9 KiB9 KiB could be saved by minifying JavaScript.
1,543 HTML elements
The page has 1,543 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify CSS
150 ms · 29 KiB29 KiB could be saved by minifying CSS.
Legacy JavaScript
150 ms · 10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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: 507 ms
507 msYour server sent the HTML in 507 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 27.8 s
27.8 sYour largest element takes 27.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 17.1 s
17.1 sVisually, the page fills in at 17.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 28.3 s
28.3 sThe page becomes fully interactive after 28.3 s. Good is under 3.8 s.
First Contentful Paint: 5.0 s
5.0 sThe first text or image appears after 5.0 s on a phone. Good is under 1.8 s.
Total Blocking Time: 774 ms
774 msScripts block taps and scrolling for 774 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
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 checks passed
Cumulative Layout Shift: 0.033
0.033The layout barely moves while loading (CLS 0.033, good is under 0.1).
Images and page weight
Page weight: 6.3 MB in 253 requests
6.3 MBYour homepage downloads 6.3 MB in 253 requests on a phone: images 3.2 MB (37), scripts 1.5 MB (90) and fonts 946 KiB (27). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
74 KiB1 image is downloaded at several times the size a phone draws it, for example logo99.png at 600 px wide, shown at 134 px. Resized copies would save about 74 KiB.
3 images in older formats
3 images (463 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.
6 images below the first screen load straight away
6 images further down the page (128 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.8 g of CO₂ per visit
1.78 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.78 g of CO₂e: 213.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
ARIA progressbar nodes must have an accessible name (1 element)
ARIA progressbar nodes must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h3 → h6 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 30 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No XML sitemap
No XML sitemap at https://pazinoecc.com/sitemap_index.xml, so Google discovers your pages only by following links.
81 internal links, 2 external
The homepage links to 81 pages on pazinoecc.com and 2 external pages.
7 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Pazino ECC is a trusted real estate and construction company in Ibeju-Lekki, Lagos. Explore secure, titled land schemes…”.
One H1 headline
Your main headline reads: “PazinoECC We are a trusted provider of a wide range of products and services”.
Title: 40 characters
Your title is a healthy 40 characters: “Real Estate Company in Ibeju Lekki Lagos”.
Canonical URL set
The canonical URL is https://pazinoecc.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
3 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
llms.txt published
The site publishes https://pazinoecc.com/llms.txt (4 KiB, 48 links), a plain-text guide to the site for AI tools.
Other pages
4 pages share 2 titles
https://pazinoecc.com/construction-company-in-lagos and https://pazinoecc.com/pazinoecc-services all use the title “Construction & Dredging Company in Lagos”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://pazinoecc.com/pazinoblog, https://pazinoecc.com/pazinoecc, https://pazinoecc.com/service/interior-designs, https://pazinoecc.com/service/cctv-camera-installation and https://pazinoecc.com/service/obd-auto-fuel-booster have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://pazinoecc.com/construction-company-in-lagos and https://pazinoecc.com/pazinoecc-services use the same meta description. A description written for each page earns more clicks.
3 links to non-canonical URLs
Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://pazinoecc.com/pazinoecc, whose canonical is https://pazinoecc.com/header/pazinoecc. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
6 pages without an H1
https://pazinoecc.com/nigeria-real-estate-for-diaspora, https://pazinoecc.com/best-real-estate-company-in-nigeria, https://pazinoecc.com/best-real-estate-engineering-company-in-ibeju-lekki, https://pazinoecc.com/buy-land-in-ibeju-lekki-from-abroad, https://pazinoecc.com/real-estate-company-in-lekki-epe-expressway-2 and https://pazinoecc.com/pazinoecc have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://pazinoecc.com/pazinoecc 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 19 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
2 broken images
2 images failed to load on a phone, for example https://pazinoecc.com/wp-content/themes/csuti/assets/images/logo-dark.png.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Only about 114 words
The homepage has only about 114 words of visible text; thin pages give Google and first-time buyers little to go on.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us For More Dredging Information”.
7 calls to action
The homepage has 7 calls to action, for example “Contact Us”, “Contact Us For More Dredging Information” and “Contact Us Today.”.
2 short forms
2 short forms (5 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 1 trust badge and “1 + Satisfied Clients”.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Privacy and tracking
13 cookies set on arrival
13Opening the homepage sets 13 cookies, 1 of them by other companies (measured from a US location before any click).
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.
12 other companies contacted
Loading the homepage contacts 12 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 pazinoecc.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on pazinoecc.com, including 19 speed issues, 1 SEO issue and 1 conversion gap. 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.