Website review, no card needed

enic.pk logo

enic.pk website review

Visit site (opens in a new tab)Reviewed 5 November 202633 issues · 86 checks

This review found 33 issues worth fixing on enic.pk, 11 of them high impact, across 86 checks. The most urgent: page weight: 12.7 MB in 446 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.1 s2.4 sMay 16Oct 312.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.9 s
May 23, 20263.0 s
May 30, 20262.9 s
Jun 6, 20263.0 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.7 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20262.8 s
Aug 1, 20262.9 s
Aug 8, 20262.9 s
Aug 15, 20262.8 s
Aug 22, 20262.9 s
Aug 29, 20262.8 s
Sep 5, 20262.7 s
Sep 12, 20262.7 s
Sep 19, 20262.6 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.6 s
Oct 24, 20262.7 s
Oct 31, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
203 ms127 msMay 16Oct 31146 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026175 ms
May 23, 2026167 ms
May 30, 2026164 ms
Jun 6, 2026182 ms
Jun 13, 2026143 ms
Jun 20, 2026136 ms
Jun 27, 2026147 ms
Jul 4, 2026147 ms
Jul 11, 2026194 ms
Jul 18, 2026194 ms
Jul 25, 2026186 ms
Aug 1, 2026178 ms
Aug 8, 2026189 ms
Aug 15, 2026194 ms
Aug 22, 2026179 ms
Aug 29, 2026177 ms
Sep 5, 2026178 ms
Sep 12, 2026177 ms
Sep 19, 2026192 ms
Sep 26, 2026188 ms
Oct 3, 2026159 ms
Oct 10, 2026155 ms
Oct 17, 2026153 ms
Oct 24, 2026147 ms
Oct 31, 2026146 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

Full-page screenshot of enic.pk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. enic.pk at 0.6 s0.6 s
  2. enic.pk at 1.2 s1.2 s
  3. enic.pk at 1.8 s1.8 s
  4. enic.pk at 2.4 s2.4 s
  5. enic.pk at 3.0 s3.0 s
  6. enic.pk at 3.6 s3.6 s
  7. enic.pk at 4.2 s4.2 s
  8. enic.pk at 4.8 s4.8 s

Speed

9 to fix77
  • Render-blocking requests

    1.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google/Doubleclick Ads, Google Tag Manager and Google CDN and others), adding 3.2 MB and 1.5 s of main-thread time.

  • Reduce unused JavaScript

    1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page.

  • Mobile performance score: 77

    77/100

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

  • Google/Doubleclick Ads adds 645 ms

    645 ms

    Google/Doubleclick Ads costs a phone 645 ms of main-thread work and 1.1 MB 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.

  • Use efficient cache lifetimes

    537 KiB

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

  • Main-thread work: 3.8 s

    A phone's processor spends 3.8 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Google Tag Manager adds 294 ms

    294 ms

    Google Tag Manager costs a phone 294 ms of main-thread work and 508 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.

  • Google CDN adds 163 ms

    163 ms

    Google CDN costs a phone 163 ms of main-thread work and 754 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.

  • 6 long tasks on the main thread

    6 long tasks block the main thread while loading, the longest for 189 ms. During a long task the page ignores taps.

  • Improve image delivery

    59 KiB

    10 images could be 59 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify JavaScript

    59 KiB

    59 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    16 KiB

    About 16 KiB of CSS is downloaded but never applied on this page.

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

1 checks passed
  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

3 to fix100
  • Time to Interactive: 26.7 s

    26.7 s

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

  • Speed Index: 10.8 s

    10.8 s

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

  • Cumulative Layout Shift: 0.216

    0.216

    The layout shifts by 0.216 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Largest content (LCP) held steady for real visitors

    -9%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.4 s

    1.4 s

    Real visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 797 ms

    797 ms

    Real visitors wait 797 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 14% faster for real visitors

    -14%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 175 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 198 ms

    198 ms

    Scripts block the page for only 198 ms while loading. Good is under 200 ms.

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 0.9 s

    0.9 s

    Your largest element renders in 0.9 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Online presence. A directory listing gives your business a …”.

Images and page weight

1 to fix70
  • Page weight: 12.7 MB in 446 requests

    12.7 MB

    Your homepage downloads 12.7 MB in 446 requests on a phone: media 8.8 MB (9), scripts 2.6 MB (105) and HTML 469 KiB (28). Under 2 MB keeps phones on slow connections fast.

  • About 3.6 g of CO₂ per visit

    3.61 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

8 to fixGoogle 8388
  • 11 tap targets too small

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

  • Links look like plain text

    2 links inside paragraphs rely on colour alone to stand out.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (65 elements)

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 20 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10099
  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 166 internal links, 55 external

    The homepage links to 166 pages on enic.pk and 55 external pages.

8 checks passed
  • Meta description: 133 characters

    Your meta description is 133 characters: “Enic.pk — Pakistan's online business directory and yellow pages. Find and list companies, services and professionals ac…”.

  • One H1 headline

    Your main headline reads: “Pakistan Business Directory & Yellow Pages”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “Pakistan Business Directory and Yellow Pages”.

  • Canonical URL set

    The canonical URL is https://enic.pk/.

  • Structured data in place

    Structured data found: Organization 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://enic.pk/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://enic.pk/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 (1,651 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix75
  • 1 page without a title

    https://enic.pk/sitemap has no <title>, so Google invents the link text in results.

  • 1 page without a meta description

    https://enic.pk/store/product/o-gin has no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://enic.pk/blog, https://enic.pk/write_for_us.html, https://enic.pk/store/product/o-gin and https://enic.pk/privacy_policy.html have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://enic.pk/store/product/o-gin took over 3 s to send its HTML from our server.

  • 12 internal pages checked

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

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

3 to fixGoogle 5485
  • 25 small tap targets

    25 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 third-party cookies

    3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “TagError: adsbygoogle.push() error: Only one 'enable_page_level_ads' allowed per page.”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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.

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

  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

  • About 1,639 words of copy

    The homepage carries about 1,639 words of visible text.

4 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Sign Up”, “Sign Up — Premium” and “Signup Pro »”.

  • 1 short form

    A short form (2 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 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.

  • 32 other companies contacted

    Loading the homepage contacts 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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 enic.pk, 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
Analytics
Google Analytics | Google Tag Manager
Hosting
WHG Hosting Services Ltd

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on enic.pk, including 12 speed issues, 1 SEO issue 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25