Website review, no card needed

lam.com.do logo

lam.com.do website review

Visit site (opens in a new tab)Reviewed 28 October 202645 issues · 81 checks

This review found 45 issues worth fixing on lam.com.do, 20 of them high impact, across 81 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
5.2 s4.3 sMay 9Oct 245.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.7 s
May 16, 20264.6 s
May 23, 20264.5 s
May 30, 20264.5 s
Jun 6, 20264.4 s
Jun 13, 20264.5 s
Jun 20, 20264.5 s
Jun 27, 20264.6 s
Jul 4, 20264.7 s
Jul 11, 20264.6 s
Jul 18, 20264.6 s
Jul 25, 20264.5 s
Aug 1, 20264.5 s
Aug 8, 20264.5 s
Aug 15, 20264.5 s
Aug 22, 20264.5 s
Aug 29, 20264.5 s
Sep 5, 20264.5 s
Sep 12, 20264.5 s
Sep 19, 20264.4 s
Sep 26, 20264.5 s
Oct 3, 20264.6 s
Oct 10, 20264.8 s
Oct 17, 20265.0 s
Oct 24, 20265.1 s
Real-visitor tap response (INP)75th percentile, phones
153 ms129 msMay 9Oct 24138 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026142 ms
May 16, 2026146 ms
May 23, 2026144 ms
May 30, 2026144 ms
Jun 6, 2026141 ms
Jun 13, 2026143 ms
Jun 20, 2026145 ms
Jun 27, 2026144 ms
Jul 4, 2026150 ms
Jul 11, 2026137 ms
Jul 18, 2026138 ms
Jul 25, 2026136 ms
Aug 1, 2026133 ms
Aug 8, 2026136 ms
Aug 15, 2026132 ms
Aug 22, 2026134 ms
Aug 29, 2026136 ms
Sep 5, 2026136 ms
Sep 12, 2026139 ms
Sep 19, 2026136 ms
Sep 26, 2026136 ms
Oct 3, 2026137 ms
Oct 10, 2026137 ms
Oct 17, 2026140 ms
Oct 24, 2026138 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 lam.com.do (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lam.com.do at 1.0 s1.0 s
  2. lam.com.do at 2.0 s2.0 s
  3. lam.com.do at 3.1 s3.1 s
  4. lam.com.do at 4.1 s4.1 s
  5. lam.com.do at 5.1 s5.1 s
  6. lam.com.do at 6.1 s6.1 s
  7. lam.com.do at 7.2 s7.2 s
  8. lam.com.do at 8.2 s8.2 s

Speed

8 to fix63
  • Render-blocking requests

    3.3 s

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

  • Improve image delivery

    1.1 s · 1.4 MB

    4 images could be 1.4 MB 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.

  • Use efficient cache lifetimes

    350 ms · 706 KiB

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

  • Mobile performance score: 63

    63/100

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

  • Reduce unused CSS

    450 ms · 90 KiB

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

  • Font display

    400 ms

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

  • Reduce unused JavaScript

    300 ms · 45 KiB

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

  • Main-thread work: 2.0 s

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

  • Minify CSS

    150 ms · 4 KiB

    4 KiB could be saved by minifying CSS.

  • 4 long tasks on the main thread

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (jQuery CDN, JSDelivr CDN and Google Fonts and others), adding 119 KiB and 46 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.

1 checks passed
  • Server response: 321 ms

    321 ms

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

Core Web Vitals

10 to fix33
  • 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: 6.5 s

    6.5 s

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

  • Real-user CLS: 0.38

    0.38

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

  • Real-user FCP: 3.9 s

    3.9 s

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

  • Real-user TTFB: 2.1 s

    2.1 s

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

  • Largest Contentful Paint: 19.8 s

    19.8 s

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

  • Time to Interactive: 20.6 s

    20.6 s

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

  • Speed Index: 9.4 s

    9.4 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • 10 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -3%

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

  • Largest content (LCP) held steady for real visitors

    +8%

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

3 checks passed
  • Real-user INP: 165 ms

    165 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 13 ms

    13 ms

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

Images and page weight

3 to fix40
  • Page weight: 11.5 MB in 93 requests

    11.5 MB

    Your homepage downloads 11.5 MB in 93 requests on a phone: media 6.5 MB (2), images 4.2 MB (25) and scripts 265 KiB (28). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    622 KiB

    4 images are downloaded at several times the size a phone draws them, for example slideshow-home-3.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 622 KiB.

  • 5 images in older formats

    5 images (1.2 MB) 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.

  • 8 images below the first screen load straight away

    8 images further down the page (263 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.2 g of CO₂ per visit

    3.25 g

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

Accessibility

9 to fixGoogle 8589
  • 18 text elements with low contrast

    18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 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. 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 8569
  • 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.

  • Title is short (25 characters)

    Your title is only 25 characters: “Inicio - Laboratorios LAM”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No XML sitemap

    No XML sitemap at https://lam.com.do/sitemap_index.xml, so Google discovers your pages only by following links.

  • 52 internal links, 9 external

    The homepage links to 52 pages on lam.com.do and 9 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://lam.com.do/.

  • 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

1 to fix83
  • 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://lam.com.do/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

3 to fix65
  • 7 linked pages are broken

    Your homepage links to https://lam.com.do/producto/cefibiotic-tabletas, https://lam.com.do/producto/rosuvastatina-40-100, https://lam.com.do/producto/deflazacort-lam-30-mg, https://lam.com.do/producto/cardilat-plus-d-100-10-25, https://lam.com.do/producto/praxeto-5 and https://lam.com.do/producto/vitavida-sabor-fresa and 1 other, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 8 pages without a meta description

    https://lam.com.do/sobre-nosotros, https://lam.com.do/capital-humano, https://lam.com.do/vademecum, https://lam.com.do/gestion-de-calidad, https://lam.com.do/planta-de-produccion and https://lam.com.do/noticias and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://lam.com.do/contacto has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://lam.com.do/contacto 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 16 found) and read each the way a search engine does.

4 checks passed
  • 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.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9271
  • 1 broken image

    1 image failed to load on a phone, for example https://lam.com.do/newchat/assets/img/logo.png.

  • 3 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 99 words

    The homepage has only about 99 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.

2 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Start Chat”.

  • 3 short forms

    3 short forms (3 fields 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.

  • 5 other companies contacted

    Loading the homepage contacts 5 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 lam.com.do, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2023.

Stack

CMS
WordPress
Framework
jQuery
Hosting
Hostinger

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on lam.com.do, including 18 speed issues, 4 SEO issues and 4 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