Website review, no card needed
pichalinen.com website review
Visit site (opens in a new tab)Reviewed 20 November 202635 issues · 74 checks
This review found 35 issues worth fixing on pichalinen.com, 14 of them high impact, across 74 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
72CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
15.3 s · 2.8 MB25 files are served with short cache lifetimes, so returning visitors download them again (2.8 MB).
Reduce unused CSS
6.5 s · 957 KiBAbout 957 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 6.5 s faster on a phone.
Render-blocking requests
6.8 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.8 s.
Minify CSS
4.2 s · 557 KiB557 KiB could be saved by minifying CSS.
Reduce unused JavaScript
1.4 s · 241 KiBAbout 241 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Improve image delivery
1.1 s · 187 KiB4 images could be 187 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: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
5 third-party services on the page
5 third-party services load with your homepage (Google Maps, jQuery CDN and Bootstrap CDN and others), adding 298 KiB and 62 ms of main-thread time.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Document request latency
32 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
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.
2 checks passed
Main-thread work: 0.4 s
A phone's processor spends 0.4 s on main-thread work while loading, 131 ms of it running JavaScript. That is comfortably low.
Server response: 56 ms
56 msYour server sent the HTML in 56 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 19.7 s
19.7 sYour largest element takes 19.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
First Contentful Paint: 7.6 s
7.6 sThe first text or image appears after 7.6 s on a phone. Good is under 1.8 s.
Time to Interactive: 19.8 s
19.8 sThe page becomes fully interactive after 19.8 s. Good is under 3.8 s.
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
10 images without width and height
10 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.
2 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.0 MB in 34 requests
3.0 MBYour homepage downloads 3.0 MB in 34 requests on a phone: images 1.4 MB (13), stylesheets 993 KiB (8) and scripts 487 KiB (9). Under 2 MB keeps phones on slow connections fast.
6 images in older formats
6 images (490 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 below the first screen load straight away
3 images further down the page (278 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.85 g of CO₂e: 102.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Page language is “zxx”
The page declares lang=“zxx”, which is not a usable language code (“zxx” means “no linguistic content”), so screen readers and translation tools guess.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 11 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (3624 characters)
Your title is 3624 characters, so Google will cut it off around 60: “:: Picha, Picha linen, linen in Lebanon, linen company in Lebanon, linen companies Lebano…”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (3621 characters)
Your meta description is 3621 characters; Google truncates after about 160, so the end of your pitch is cut.
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 XML sitemap
No XML sitemap at https://pichalinen.com/sitemap.xml, so Google discovers your pages only by following links.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
83 internal links, 3 external
The homepage links to 83 pages on pichalinen.com and 3 external pages.
1 checks passed
robots.txt in place
robots.txt is in place.
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://pichalinen.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.
1 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.
Other pages
8 pages share a title
https://pichalinen.com/bedding.php, https://pichalinen.com/categories.php, https://pichalinen.com/kitchen.php, https://pichalinen.com/bath.php, https://pichalinen.com/kids.php and https://pichalinen.com/Customized.php and 2 others all use the title “:: Picha, Picha linen, linen in Lebanon, linen company in Lebanon, li…”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages share a meta description
https://pichalinen.com/bedding.php, https://pichalinen.com/categories.php, https://pichalinen.com/kitchen.php, https://pichalinen.com/bath.php, https://pichalinen.com/kids.php and https://pichalinen.com/Customized.php and 2 others use the same meta description. A description written for each page earns more clicks.
8 pages without an H1
https://pichalinen.com/bedding.php, https://pichalinen.com/categories.php, https://pichalinen.com/kitchen.php, https://pichalinen.com/bath.php, https://pichalinen.com/kids.php and https://pichalinen.com/Customized.php and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://pichalinen.com/categories.php 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.
8 internal pages checked
We fetched 8 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 8 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 8 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 8 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
21 of 26 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 94 words
The homepage has only about 94 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.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact” and “Subscribe”.
3 calls to action
The homepage has 3 calls to action, for example “Contact” and “Subscribe”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
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.
7 other companies contacted
Loading the homepage contacts 7 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 pichalinen.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Hosting
- InMotion Hosting, Inc.
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 pichalinen.com, including 12 speed issues, 8 SEO issues and 3 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.