Website review, no card needed

ortigamar.com logo

ortigamar.com website review

Visit site (opens in a new tab)Reviewed 18 November 202651 issues · 79 checks

This review found 51 issues worth fixing on ortigamar.com, 22 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. 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

Full-page screenshot of ortigamar.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ortigamar.com at 0.8 s0.8 s
  2. ortigamar.com at 1.7 s1.7 s
  3. ortigamar.com at 2.5 s2.5 s
  4. ortigamar.com at 3.3 s3.3 s
  5. ortigamar.com at 4.1 s4.1 s
  6. ortigamar.com at 5.0 s5.0 s
  7. ortigamar.com at 5.8 s5.8 s
  8. ortigamar.com at 6.6 s6.6 s

Speed

14 to fix42
  • Use efficient cache lifetimes

    5.2 s · 1.8 MB

    34 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).

  • Render-blocking requests

    6.3 s

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

  • Reduce unused JavaScript

    1.9 s · 339 KiB

    About 339 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • Improve image delivery

    1.4 s · 738 KiB

    7 images could be 738 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

  • Document request latency

    1.8 s · 30 KiB

    The HTML itself could arrive about 1.8 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    1.8 s

    Reduce initial server response time. Google estimates savings of 1.8 s on a phone.

  • Reduce unused CSS

    1.4 s · 249 KiB

    About 249 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Mobile performance score: 42

    42/100

    Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Server response: 1.9 s

    1.9 s

    Your server takes 1.9 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Font display

    700 ms

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (netsearch.pt, Other Google APIs/SDKs and Google Fonts and others), adding 2.0 MB and 367 ms of main-thread time.

  • Minify CSS

    450 ms · 61 KiB

    61 KiB could be saved by minifying CSS.

  • Minify JavaScript

    450 ms · 49 KiB

    49 KiB could be saved by minifying JavaScript.

  • netsearch.pt adds 243 ms

    243 ms

    netsearch.pt costs a phone 243 ms of main-thread work and 1.8 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.

  • 3 long tasks on the main thread

    3 long tasks block the main thread while loading, the longest for 77 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 checks passed
  • Main-thread work: 1.2 s

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

Core Web Vitals

6 to fix48
  • First Contentful Paint: 8.3 s

    8.3 s

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

  • 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: 10.5 s

    10.5 s

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

  • Time to Interactive: 13.9 s

    13.9 s

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

  • Cumulative Layout Shift: 0.276

    0.276

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

  • 4 images without width and height

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

1 checks passed
  • Total Blocking Time: 49 ms

    49 ms

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

Images and page weight

2 to fix75
  • Page weight: 2.1 MB in 53 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 53 requests on a phone: images 1.1 MB (18), scripts 603 KiB (16) and stylesheets 256 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    21 KiB

    2 images are downloaded at several times the size a phone draws them, for example 11.jpg at 1,125 px wide, shown at 359 px. Resized copies would save about 21 KiB.

  • 4 images in older formats

    4 images (358 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.

  • About 0.6 g of CO₂ per visit

    0.59 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

9 to fixGoogle 8083
  • Frames without titles

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 3 images without alt text

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 5 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

1 checks passed
  • 27 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 34 WCAG 2.2 A/AA and best-practice rules on the phone render: 27 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

8 to fixGoogle 9261
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (197 characters)

    Your title is 197 characters, so Google will cut it off around 60: “ORTIGA MAR | Produtos Congelados, Fornecedor congelados comercio peixe carne congelada, m…”.

  • Canonical points to another host

    Your canonical URL points to netsearch.pt, not ortigamar.com, so Google may credit that host instead.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (1730 characters)

    Your meta description is 1730 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 robots.txt

    There is no robots.txt at ortigamar.com/robots.txt, the first file search crawlers ask for.

  • No favicon declared

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

  • No X (Twitter) card tag

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

  • 10 internal links, 15 external

    The homepage links to 10 pages on ortigamar.com and 15 external pages.

1 checks passed
  • XML sitemap found

    Your XML sitemap is reachable at http://ortigamar.com/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://ortigamar.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

4 to fix71
  • 4 pages without a title

    https://ortigamar.com/produtos-produtos, https://ortigamar.com/servicos-servicos, https://ortigamar.com/galeria-solucoes-integradas-de-vendas and https://ortigamar.com/contactos-contactos have no <title>, so Google invents the link text in results.

  • 2 pages share a title

    / and https://ortigamar.com/index-empresa all use the title “ORTIGA MAR | Produtos Congelados, Fornecedor congelados comercio peix…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages share a meta description

    https://ortigamar.com/index-empresa, https://ortigamar.com/produtos-produtos, https://ortigamar.com/servicos-servicos, https://ortigamar.com/galeria-solucoes-integradas-de-vendas and https://ortigamar.com/contactos-contactos use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://ortigamar.com/index-empresa, https://ortigamar.com/produtos-produtos, https://ortigamar.com/servicos-servicos, https://ortigamar.com/galeria-solucoes-integradas-de-vendas and https://ortigamar.com/contactos-contactos have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://ortigamar.com/index-empresa, https://ortigamar.com/produtos-produtos, https://ortigamar.com/servicos-servicos, https://ortigamar.com/galeria-solucoes-integradas-de-vendas and https://ortigamar.com/contactos-contactos 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.

  • 4 pages slow to respond

    https://ortigamar.com/index-empresa, https://ortigamar.com/produtos-produtos, https://ortigamar.com/servicos-servicos and https://ortigamar.com/galeria-solucoes-integradas-de-vendas took over 3 s to send their HTML from our server.

  • 5 internal pages checked

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

4 checks passed
  • Linked pages load

    All 5 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 5 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

1 to fixGoogle 7092
  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://www.netsearch.pt/layout2015/css/fonts/awesome/fonts/fontawesome-webfont.woff2?v=4.7.0' from …”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix36
  • 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.

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

  • Only about 52 words

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

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

1 checks passed
  • 1 short form

    A short form (0 fields at most) is 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.

  • 8 other companies contacted

    Loading the homepage contacts 8 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 ortigamar.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
Flesk As Dmns Dominios, S.A.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 51 issues on ortigamar.com, including 20 speed issues, 8 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