Website review, no card needed
gohartextile.com website review
Visit site (opens in a new tab)Reviewed 3 November 202635 issues · 80 checks
This review found 35 issues worth fixing on gohartextile.com, 13 of them high impact, across 80 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.0 s |
| May 23, 2026 | 3.7 s |
| May 30, 2026 | 3.9 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 3.7 s |
| Jun 20, 2026 | 3.8 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 4.0 s |
| Jul 11, 2026 | 4.0 s |
| Jul 18, 2026 | 4.0 s |
| Jul 25, 2026 | 3.7 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.8 s |
| Aug 15, 2026 | 4.1 s |
| Aug 22, 2026 | 4.4 s |
| Aug 29, 2026 | 4.2 s |
| Sep 5, 2026 | 4.2 s |
| Sep 12, 2026 | 4.0 s |
| Sep 19, 2026 | 3.6 s |
| Sep 26, 2026 | 3.9 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 4.0 s |
| Oct 24, 2026 | 3.9 s |
| Oct 31, 2026 | 4.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 142 ms |
| May 23, 2026 | 144 ms |
| May 30, 2026 | 158 ms |
| Jun 6, 2026 | 148 ms |
| Jun 13, 2026 | 141 ms |
| Jun 20, 2026 | 142 ms |
| Jun 27, 2026 | 142 ms |
| Jul 4, 2026 | 144 ms |
| Jul 11, 2026 | 147 ms |
| Jul 18, 2026 | 144 ms |
| Jul 25, 2026 | 141 ms |
| Aug 1, 2026 | 131 ms |
| Aug 8, 2026 | 131 ms |
| Aug 15, 2026 | 141 ms |
| Aug 22, 2026 | 141 ms |
| Aug 29, 2026 | 141 ms |
| Sep 5, 2026 | 134 ms |
| Sep 12, 2026 | 126 ms |
| Sep 19, 2026 | 125 ms |
| Sep 26, 2026 | 128 ms |
| Oct 3, 2026 | 126 ms |
| Oct 10, 2026 | 129 ms |
| Oct 17, 2026 | 128 ms |
| Oct 24, 2026 | 137 ms |
| Oct 31, 2026 | 137 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Use efficient cache lifetimes
1.4 s · 374 KiB55 files are served with short cache lifetimes, so returning visitors download them again (374 KiB).
Render-blocking requests
1.8 s23 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 85
85/100Your mobile performance score is 85. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
600 ms · 109 KiBAbout 109 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Improve image delivery
200 ms · 16 KiB1 image could be 16 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Reduce unused CSS
150 ms · 12 KiBAbout 12 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 99 ms. During a long task the page ignores taps.
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 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 54 KiB and 0 ms of main-thread time.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 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: 4.9 s
4.9 sReal visitors wait 4.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.2 s
4.2 sReal visitors see the first content after 4.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.9 s
2.9 sReal visitors wait 2.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 3.7 s
3.7 sYour largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “At Gohar Textile we ensure affordable quality is brought to…”. Most of its time is element render delay (1.9 s).
Speed Index: 4.6 s
4.6 sVisually, the page fills in at 4.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 4.1 s
4.1 sThe page becomes fully interactive after 4.1 s. Good is under 3.8 s.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 142 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.0 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 138 ms
138 msReal visitors wait 138 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Total Blocking Time: 56 ms
56 msScripts block the page for only 56 ms while loading. Good is under 200 ms.
Images and page weight
2 images in older formats
2 images (691 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.
4 images far larger than shown
438 KiB4 images are downloaded at several times the size a phone draws them, for example Gohar-Textile-Mills-Spinning-Drone.jpg at 1,619 px wide, shown at 390 px. Resized copies would save about 438 KiB.
About 0.2 g of CO₂ per visit
0.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.20 g of CO₂e: 24.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 738 KiB in 60 requests
738 KiBYour homepage downloads 738 KiB in 60 requests on a phone: scripts 345 KiB (27), images 246 KiB (8) and stylesheets 68 KiB (22). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 22 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 3 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.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
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.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
32 internal links, 0 external
The homepage links to 32 pages on gohartextile.com and 0 external pages.
4 checks passed
Title: 65 characters
Your title is a healthy 65 characters: “Gohar Textile Mills Pvt Ltd. – A home textile company in Pakistan”.
Canonical URL set
The canonical URL is https://www.gohartextile.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.gohartextile.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.gohartextile.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 (341 words), so crawlers that don't run JavaScript still read it.
Other pages
12 pages without a meta description
https://www.gohartextile.com/products, https://www.gohartextile.com/social-responsiability, https://www.gohartextile.com/career, https://www.gohartextile.com/announcements, https://www.gohartextile.com/contact-us and https://www.gohartextile.com/spinning and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages with very little text
https://www.gohartextile.com/products, https://www.gohartextile.com/career, https://www.gohartextile.com/announcements, https://www.gohartextile.com/contact-us, https://www.gohartextile.com/spinning and https://www.gohartextile.com/weaving and 4 others have 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.
12 internal pages checked
We fetched 12 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 12 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.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://www.gohartextile.com/wp-content/uploads/2018/11/quote-1.png.
2 small tap targets
2 of 8 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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 ()”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 321 words of copy
The homepage carries about 321 words of visible text.
1 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Download Brochure”, “Contact Us” and “Learn More”.
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.
2 other companies contacted
Loading the homepage contacts 2 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 gohartextile.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
- Hosting
- Namecheap
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 gohartextile.com, including 14 speed issues, 5 SEO issues and 6 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.