Website review, no card needed

biemilac.com.tr logo

biemilac.com.tr website review

Visit site (opens in a new tab)Reviewed 18 October 202631 issues · 74 checks

This review found 31 issues worth fixing on biemilac.com.tr, 13 of them high impact, across 74 checks. The most urgent: render-blocking 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
2.6 s1.6 sApr 25Oct 102.4 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.9 s
May 2, 20262.2 s
May 9, 20262.2 s
May 16, 20262.1 s
May 23, 20261.9 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20262.0 s
Jul 18, 20262.2 s
Jul 25, 20262.3 s
Aug 1, 20262.4 s
Aug 8, 20262.5 s
Aug 15, 20262.4 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.5 s
Oct 10, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
134 ms80 msApr 25Oct 10105 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202691 ms
May 2, 202696 ms
May 9, 202694 ms
May 16, 202692 ms
May 23, 202689 ms
May 30, 202686 ms
Jun 6, 202689 ms
Jun 13, 202686 ms
Jun 20, 202687 ms
Jun 27, 202687 ms
Jul 4, 202686 ms
Jul 11, 202686 ms
Jul 18, 202692 ms
Jul 25, 2026104 ms
Aug 1, 2026114 ms
Aug 8, 2026118 ms
Aug 15, 2026109 ms
Aug 22, 202696 ms
Aug 29, 2026102 ms
Sep 5, 2026104 ms
Sep 12, 2026108 ms
Sep 19, 2026128 ms
Sep 26, 2026115 ms
Oct 3, 2026111 ms
Oct 10, 2026105 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 biemilac.com.tr (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. biemilac.com.tr at 0.9 s0.9 s
  2. biemilac.com.tr at 1.9 s1.9 s
  3. biemilac.com.tr at 2.8 s2.8 s
  4. biemilac.com.tr at 3.7 s3.7 s
  5. biemilac.com.tr at 4.7 s4.7 s
  6. biemilac.com.tr at 5.6 s5.6 s
  7. biemilac.com.tr at 6.5 s6.5 s
  8. biemilac.com.tr at 7.4 s7.4 s

Speed

5 to fix60
  • Render-blocking requests

    2.4 s

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

  • Reduce unused CSS

    900 ms · 131 KiB

    About 131 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Mobile performance score: 60

    60/100

    Your mobile performance score is 60 (desktop: 80). Pages that score under 90 lose visitors before the first paint.

  • Font display

    600 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 600 ms).

  • Improve image delivery

    300 ms · 36 KiB

    1 image could be 36 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Reduce unused JavaScript

    150 ms · 39 KiB

    About 39 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 2 long tasks on the main thread

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 132 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.

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 267 ms of it running JavaScript. That is comfortably low.

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

10 to fix67
  • 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.

  • Largest Contentful Paint: 11.8 s

    11.8 s

    Your largest element takes 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 9.1 s

    9.1 s

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

  • Time to Interactive: 12.1 s

    12.1 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

    The first text or image appears after 3.5 s on a phone. Good is under 1.8 s.

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Largest content (LCP) got 21% slower for real visitors

    +21%

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • 21 images without width and height

    21 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) got 16% slower for real visitors

    +16%

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

4 checks passed
  • Real-user INP: 122 ms

    122 ms

    Real visitors wait 122 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.023

    0.023

    The layout barely moves while loading (CLS 0.023, good is under 0.1).

  • Total Blocking Time: 37 ms

    37 ms

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

Images and page weight

2 to fix60
  • Page weight: 4.8 MB in 64 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 64 requests on a phone: media 2.1 MB (1), images 2.1 MB (18) and fonts 204 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    175 KiB

    2 images are downloaded at several times the size a phone draws them, for example IMG-20250317-WA0015.jpg at 1,920 px wide, shown at 250 px. Resized copies would save about 175 KiB.

  • 5 images in older formats

    5 images (454 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.

  • 1 image below the first screen load straight away

    1 image further down the page (65 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.4 g of CO₂ per visit

    1.35 g

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

Accessibility

1 to fixGoogle 10098
  • 9 images without alt text

    9 images have no alt text, which hurts accessibility and image search.

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 42 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: 42 passed and 0 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9273
  • 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.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 73 internal links, 3 external

    The homepage links to 73 pages on biemilac.com.tr and 3 external pages.

4 checks passed
  • Title: 30 characters

    Your title is a healthy 30 characters: “Biem İlaç – İlk Çare, Tek Çare”.

  • Canonical URL set

    The canonical URL is https://www.biemilac.com.tr/.

  • 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.biemilac.com.tr/wp-sitemap.xml.

AI search readiness

1 to fix83
  • 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.biemilac.com.tr/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

1 to fix95
  • 15 pages without a meta description

    https://www.biemilac.com.tr/hakkimizda, https://www.biemilac.com.tr/urunler, https://www.biemilac.com.tr/uretim-tesisi, https://www.biemilac.com.tr/ar-ge, https://www.biemilac.com.tr/is-gelistirme and https://www.biemilac.com.tr/yurt-ici-pazar and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages slow to respond

    https://www.biemilac.com.tr/yurtdisi-pazarlar, https://www.biemilac.com.tr/lisansorluk, https://www.biemilac.com.tr/yatirimci-iliskileri, https://www.biemilac.com.tr/yonetim-kurulu and https://www.biemilac.com.tr/kurumsal-bilgiler took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.

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

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10092
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix50
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 86 words

    The homepage has only about 86 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

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

  • 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
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 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 biemilac.com.tr, 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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on biemilac.com.tr, including 15 speed issues, 4 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

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