Scanned sites / www.puertomazatlan.com.mx / 2026-10-22-1911

www.puertomazatlan.com.mx scan from 2026-10-22 19:11:44 UTC DR 36

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

Scan 2026-10-22-1911

Scanned 2026-10-22 19:11:44 UTC, finished 2026-10-23 01:17:01 UTC

Site: https://www.puertomazatlan.com.mx/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

9/ 100Poor

On October 22, 2026 the Site Spider crawled 1381 pages and 2230 assets of www.puertomazatlan.com.mx, starting from https://www.puertomazatlan.com.mx/. It scored 9 out of 100, a poor result. 14 of 33 checks found something to fix, led by broken links (925), non-200 responses (1,002), indexability (183); 9 checks passed. Most of the points went to broken links (−20), non-200 responses (−10), indexability (−10). 10 checks found something the score does not count, listed as noted. 4 checks were not run because the crawl fetched nothing for them. The list below shows each check's result, the fix plan, when present, explains what to do first, and the security review at the end of the page covers headers, transport, libraries and exposed files.

Security review: Medium2 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
1381
Assets fetched
2230
Status
Completed
Checks with issues
14 of 33
CoverageJob finished, partial coverage

3,611 of 3,805 discovered URLs were fetched, 189 failed, 74 left out by the 5,000-page and 1,000-asset budget. The job finished, but the crawl did not reach everything it found. HTML only: nothing here ran JavaScript. 87 link destinations on other sites were checked.

  • Title tags61 issues
    61 of 183 pages have title issues.
    −3.3 points
  • Meta descriptions183 issues
    183 of 183 pages have meta description issues.
    −8 points
  • Headings182 issues
    182 of 183 pages have heading issues.
    −6 points
  • Broken links925 issues
    965 internal links point at 925 broken URLs.
    −20 points
  • Links to other sites8 issues
    8 destinations answered with an error, 53 could not be determined (timeouts, rate limits or refusals), of 87 destinations checked.
    −1.8 points
  • Redirects161 issues
    385 redirecting URLs, 6 of them chained.
    −3.5 points
  • Non-200 responses1,002 issues
    1404 URLs did not return a 2xx response. 1387 of them are pages, 1002 with an error status; the rest are assets or redirects.
    −10 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability183 issues
    183 of 183 indexable pages have indexability warnings.
    −10 points
  • Image alt text192 issues
    192 of 3150 image references have no alt attribute. 217 use an empty alt (decorative), which is fine.
    −0.4 points
  • Heavy assets27 issues
    27 assets larger than 500 KB among 2230 fetched assets. 870 documents over that size are listed but not counted: downloads are not page weight.
    −6 points
  • Orphan pages142 issues
    142 pages have no internal links pointing at them.
    −3.1 points
  • Sitemap coverage409 issues
    1 sitemap listing 228 URLs: 182 crawled pages missing, 227 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −6 points
  • Internal link counts13 noted
    Internal link counts for 183 pages; 13 worth a look.
  • Thin content118 issues
    118 of 183 pages have fewer than 200 words.
    −5.2 points
  • Duplicate content814 issues
    4 groups of pages with identical HTML.
    −8 points
  • URL format777 noted
    777 of 1381 page URLs are harder to read, share or cache than they need to be.
  • Canonicals183 noted
    183 of 183 pages have a canonical worth checking.
  • Robots directivesOK
    No page carries a robots directive; all 183 pages are open to search engines.
  • Anchor text698 noted
    698 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure5 noted
    5 of 183 pages could use the title, heading and snippet space better.
  • Image weight and alt length69 noted
    69 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies149 noted
    149 URLs answered in a way worth looking at.
  • HTML and head validation11 noted
    11 of 183 pages have HTML problems: 11 with head tags outside <head>, 0 over 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    No page carries structured data (183 indexable pages checked).
  • Near duplicates2 noted
    2 pages in 1 group read almost the same as another page (95% alike or more).
  • Soft 404sOK
    None of 183 pages answering 200 reads like an error page.
  • AccessibilityNot checked
    Not checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
  • Link positionsOK
    0 of 37 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    No page declares rel=next or rel=prev pagination.
  • Headers and cookiesOK
    0 cookies set by the site; 13 response headers recorded across 3611 URLs.
  • Orphans in searchNot checked
    Not checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
  • Link ScoreOK
    Link Score (internal PageRank, 0-100) for 183 pages; 161 hold almost none (10 or less).
  • JavaScript renderingNot checked
    Not checked: this scan did not render pages. Tick "Include JavaScript rendering checks" when you request a scan to compare the served HTML with what a browser builds.
  • PageSpeed InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • Spelling156 noted
    156 words an English dictionary does not know, on 14 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2326 sites, median 79%, average 78%

www.puertomazatlan.com.mx scores 9%, higher than 0% of the 2326 scanned sites. See the full ranking.

0571140%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 1 site15%: 0 sites16%: 0 sites17%: 0 sites18%: 0 sites19%: 0 sites20%: 0 sites21%: 1 site22%: 0 sites23%: 0 sites24%: 0 sites25%: 0 sites26%: 0 sites27%: 0 sites28%: 1 site29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 1 site34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 1 site40%: 3 sites41%: 1 site42%: 1 site43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 3 sites49%: 6 sites50%: 5 sites51%: 4 sites52%: 11 sites53%: 6 sites54%: 8 sites55%: 9 sites56%: 8 sites57%: 12 sites58%: 17 sites59%: 9 sites60%: 16 sites61%: 12 sites62%: 19 sites63%: 27 sites64%: 22 sites65%: 32 sites66%: 35 sites67%: 35 sites68%: 34 sites69%: 47 sites70%: 44 sites71%: 69 sites72%: 71 sites73%: 69 sites74%: 68 sites75%: 72 sites76%: 87 sites77%: 92 sites78%: 106 sites79%: 86 sites80%: 106 sites81%: 105 sites82%: 114 sites83%: 99 sites84%: 106 sites85%: 86 sites86%: 69 sites87%: 75 sites88%: 58 sites89%: 64 sites90%: 34 sites91%: 47 sites92%: 38 sites93%: 23 sites94%: 16 sites95%: 11 sites96%: 10 sites97%: 12 sites98%: 4 sites99%: 1 site100%: 70 sites9% here100%90%80%70%60%50%40%30%20%10%0%

Green 90% and up (Excellent), lime 75 to 89 (Good), amber 50 to 74 (Needs work), red below 50 (Poor).

Internal link map

Loading the link map...

Start page (centre)OKRedirectErrorOrphanLinked from most pagesOne inbound link or noneRings = clicks from the start page. Size = inbound links. Drag to pan, scroll to zoom, click a page to see only its links.

Fix plan

Written by gpt-4o-mini from the scan findings

The site has multiple significant issues affecting its health score. Key fixes involve addressing broken links, redirects, and the sitemap, as well as improving page titles, meta descriptions, and headings.

  1. 1

    Fix Broken Links

    Why: Resolving broken links improves user experience and enhances SEO.

    How: Identify broken links from the provided URLs and either restore the pages or remove links that no longer point to valid content.

    Checks: broken-links

  2. 2

    Address Redirects

    Why: Cleaning up redirects enhances page speed and user navigation.

    How: Evaluate and update URLs to eliminate unnecessary redirects and resolve chained redirects.

    Checks: redirects

  3. 3

    Update Sitemap

    Why: A functional sitemap is crucial for proper indexing by search engines.

    How: Correct the sitemap URL and ensure it includes all relevant pages without errors.

    Checks: sitemap-coverage

  4. 4

    Improve Title Tags

    Why: Optimizing title tags boosts rankings and click-through rates.

    How: Add missing titles and revise short or duplicate title tags as needed.

    Checks: titles

  5. 5

    Add Meta Descriptions

    Why: Meta descriptions influence click-through rates in search results.

    How: Create unique meta descriptions for all pages that currently lack them.

    Checks: meta-descriptions

  6. 6

    Ensure Proper Headings

    Why: Proper heading structure improves content readability and SEO.

    How: Add appropriate H1 tags to pages that currently lack them.

    Checks: headings

Generated automatically; verify each change against your own site before relying on it.

Security review

Written by gpt-4o-mini from 16 checks over the crawl

The website www.puertomazatlan.com.mx has several security issues that need attention, particularly regarding the absence of critical response headers, insecure forms, and the use of outdated JavaScript libraries. Addressing these can improve user privacy and security.

  • 0 high
  • 2 medium
  • 2 low
  • 1 info
  1. 1

    Forms Sending Data Over HTTPMedium

    Why it matters: Forms are sending data insecurely, which can expose user information.

    Fix: Ensure the forms on https://www.puertomazatlan.com.mx/acerca-del-puerto/cesionarios-y-pre… and https://www.puertomazatlan.com.mx/acerca-del-puerto/licitaciones/ use HTTPS endpoints.

    Evidence: Forms over HTTPS

  2. 2

    Use of Vulnerable JavaScript LibrariesMedium

    Why it matters: Outdated libraries can expose the site to various security vulnerabilities.

    Fix: Upgrade jQuery to at least version 3.5.0 and ensure all libraries are up-to-date.

    Evidence: Vulnerable JavaScript libraries

  3. 3

    Missing Referrer-Policy HeaderLow

    Why it matters: Without a Referrer-Policy, sensitive URL information is shared with third-party sites.

    Fix: Add a Referrer-Policy header to your server responses, e.g., `Referrer-Policy: no-referrer`.

    Evidence: Referrer policy

  4. 4

    Server Information DisclosureLow

    Why it matters: Revealing server versions can help attackers exploit known vulnerabilities.

    Fix: Remove or mask 'Server' and 'X-Powered-By' headers from responses.

    Evidence: Software version disclosure

  5. 5

    Missing Permissions-Policy HeaderInfo

    Why it matters: A Permissions-Policy can restrict access to unnecessary browser features.

    Fix: Add a Permissions-Policy header like `Permissions-Policy: geolocation=(), microphone=(), camera=()` to your responses.

    Evidence: Permissions policy

What the checks found

  • FoundReferrer policyLow

    No HTML page sends referrer-policy. Without a Referrer-Policy the full page address, including any query string, is sent to every site a visitor clicks through to.

    • https://www.puertomazatlan.com.mx/ → no referrer-policy
    • https://www.puertomazatlan.com.mx/servicios-portuarios/tramites-en-linea/ → no referrer-policy
    • https://www.puertomazatlan.com.mx/directorio/ → no referrer-policy
    • https://www.puertomazatlan.com.mx/home/ → no referrer-policy
    • https://www.puertomazatlan.com.mx/servicios-portuarios/programacion-de-buques/ → no referrer-policy
    • https://www.puertomazatlan.com.mx/relevante/ferries-a-la-paz/ → no referrer-policy
    • https://www.puertomazatlan.com.mx/servicios-portuarios/agencias-navieras/ → no referrer-policy
    • https://www.puertomazatlan.com.mx/servicios-portuarios/agentes-aduanales/ → no referrer-policy
    • https://www.puertomazatlan.com.mx/solicitud-de-contratos/ → no referrer-policy
    • https://www.puertomazatlan.com.mx/APIWEB/EVALUACION/EVALUACION_SERVICIOS.HTML → no referrer-policy
    • https://www.puertomazatlan.com.mx/acerca-del-puerto/cesionarios-y-prestadores-de-servicios/ → no referrer-policy
    • https://www.puertomazatlan.com.mx/transparencia/transparencia-focalizada/ → no referrer-policy
  • FoundPermissions policyInfo

    No HTML page sends permissions-policy. A Permissions-Policy header turns off browser features the site does not use (camera, microphone, geolocation), limiting what an injected script could do.

    • https://www.puertomazatlan.com.mx/ → no permissions-policy
    • https://www.puertomazatlan.com.mx/servicios-portuarios/tramites-en-linea/ → no permissions-policy
    • https://www.puertomazatlan.com.mx/directorio/ → no permissions-policy
    • https://www.puertomazatlan.com.mx/home/ → no permissions-policy
    • https://www.puertomazatlan.com.mx/servicios-portuarios/programacion-de-buques/ → no permissions-policy
    • https://www.puertomazatlan.com.mx/relevante/ferries-a-la-paz/ → no permissions-policy
    • https://www.puertomazatlan.com.mx/servicios-portuarios/agencias-navieras/ → no permissions-policy
    • https://www.puertomazatlan.com.mx/servicios-portuarios/agentes-aduanales/ → no permissions-policy
    • https://www.puertomazatlan.com.mx/solicitud-de-contratos/ → no permissions-policy
    • https://www.puertomazatlan.com.mx/APIWEB/EVALUACION/EVALUACION_SERVICIOS.HTML → no permissions-policy
    • https://www.puertomazatlan.com.mx/acerca-del-puerto/cesionarios-y-prestadores-de-servicios/ → no permissions-policy
    • https://www.puertomazatlan.com.mx/transparencia/transparencia-focalizada/ → no permissions-policy
  • FoundSoftware version disclosureLow

    Responses reveal the exact server or framework version, which lets an attacker look up known vulnerabilities for it without guessing.

    • server: Apache (3611 responses)
    • x-powered-by: PHP/8.4.27 (24 responses)
  • FoundForms over HTTPSMedium

    2 forms would send what visitors type over plain HTTP, where it can be read or changed on the way.

    • https://www.puertomazatlan.com.mx/acerca-del-puerto/cesionarios-y-pre… posts a form to http://consultapublicamx.inai.org.mx:8080/vut-web/?idSujetoObigadoParametro=11&idEntidadP… over plain HTTP
    • https://www.puertomazatlan.com.mx/acerca-del-puerto/licitaciones/ posts a form to http://consultapublicamx.inai.org.mx:8080/vut-web/?idSujetoObigadoParametro=11&idEntidadP… over plain HTTP
  • FoundVulnerable JavaScript librariesMedium

    5 libraries with published vulnerabilities: jQuery 1.10.2, jQuery 1.11.3, jQuery 3.2.1, jQuery UI 1.10.1, Bootstrap 3.1.1. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 1.10.2 in https://www.puertomazatlan.com.mx/assets/js/vendor/jquery-1.10.2.min.js: CVE-2015-9251 (XSS via cross-domain AJAX), CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
    • jQuery 1.11.3 in https://www.puertomazatlan.com.mx/acerca-del-puerto/acerca_1/jquery-1.11.3.min.…: CVE-2015-9251 (XSS via cross-domain AJAX), CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
    • jQuery 3.2.1 in https://www.puertomazatlan.com.mx/js/jquery-3.2.1.min.js: CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
    • jQuery UI 1.10.1 in https://ajax.googleapis.com/ajax/libs/jqueryui/1.10.1/jquery-ui.min.js: CVE-2016-7103, CVE-2021-41182, CVE-2021-41183, CVE-2021-41184, CVE-2022-31160 (XSS through widget options); fixed in 1.13.2
    • Bootstrap 3.1.1 in https://www.puertomazatlan.com.mx/assets/js/vendor/bootstrap.js: CVE-2016-10735, CVE-2018-14040, CVE-2018-14041, CVE-2018-14042, CVE-2019-8331 (XSS through data attributes in tooltip, popover, collapse and scrollspy); fixed in 3.4.1
  • NoteContent Security Policy

    A Content-Security-Policy is set, but it allows inline or eval scripts ('unsafe-inline' / 'unsafe-eval'), which removes most of its protection against injected scripts.

    • https://www.puertomazatlan.com.mx/ → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: https:; font-src 'self' data: https:; frame-src 'self' https://www.youtube.com https://www.youtube-nocookie.com; connect-src 'self' https:; object-src 'none'; bas
    • https://www.puertomazatlan.com.mx/servicios-portuarios/tramites-en-linea/ → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: https:; font-src 'self' data: https:; frame-src 'self' https://www.youtube.com https://www.youtube-nocookie.com; connect-src 'self' https:; object-src 'none'; bas
    • https://www.puertomazatlan.com.mx/directorio/ → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: https:; font-src 'self' data: https:; frame-src 'self' https://www.youtube.com https://www.youtube-nocookie.com; connect-src 'self' https:; object-src 'none'; bas
    • https://www.puertomazatlan.com.mx/home/ → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: https:; font-src 'self' data: https:; frame-src 'self' https://www.youtube.com https://www.youtube-nocookie.com; connect-src 'self' https:; object-src 'none'; bas
    • https://www.puertomazatlan.com.mx/servicios-portuarios/programacion-de-buques/ → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: https:; font-src 'self' data: https:; frame-src 'self' https://www.youtube.com https://www.youtube-nocookie.com; connect-src 'self' https:; object-src 'none'; bas
    • https://www.puertomazatlan.com.mx/relevante/ferries-a-la-paz/ → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: https:; font-src 'self' data: https:; frame-src 'self' https://www.youtube.com https://www.youtube-nocookie.com; connect-src 'self' https:; object-src 'none'; bas
    • https://www.puertomazatlan.com.mx/servicios-portuarios/agencias-navieras/ → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: https:; font-src 'self' data: https:; frame-src 'self' https://www.youtube.com https://www.youtube-nocookie.com; connect-src 'self' https:; object-src 'none'; bas
    • https://www.puertomazatlan.com.mx/servicios-portuarios/agentes-aduanales/ → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: https:; font-src 'self' data: https:; frame-src 'self' https://www.youtube.com https://www.youtube-nocookie.com; connect-src 'self' https:; object-src 'none'; bas
    • https://www.puertomazatlan.com.mx/solicitud-de-contratos/ → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: https:; font-src 'self' data: https:; frame-src 'self' https://www.youtube.com https://www.youtube-nocookie.com; connect-src 'self' https:; object-src 'none'; bas
    • https://www.puertomazatlan.com.mx/APIWEB/EVALUACION/EVALUACION_SERVICIOS.HTML → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: https:; font-src 'self' data: https:; frame-src 'self' https://www.youtube.com https://www.youtube-nocookie.com; connect-src 'self' https:; object-src 'none'; bas
    • https://www.puertomazatlan.com.mx/acerca-del-puerto/cesionarios-y-prestadores-de-servicios/ → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: https:; font-src 'self' data: https:; frame-src 'self' https://www.youtube.com https://www.youtube-nocookie.com; connect-src 'self' https:; object-src 'none'; bas
    • https://www.puertomazatlan.com.mx/transparencia/transparencia-focalizada/ → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: https:; font-src 'self' data: https:; frame-src 'self' https://www.youtube.com https://www.youtube-nocookie.com; connect-src 'self' https:; object-src 'none'; bas
  • NoteThird-party scripts

    Scripts run from 4 other domains without Subresource Integrity, so a compromise of any of them changes what runs on this site. (Tag managers and analytics rarely support SRI; a Content-Security-Policy that names these hosts is the usual control.)

    • www.googletagmanager.com (37 script tags)
    • framework-gb.cdn.gob.mx (37 script tags)
    • oss.maxcdn.com (35 script tags)
    • cdnjs.cloudflare.com (35 script tags)
7 checks passed, 2 not applicable
  • OKHTTPS

    All 183 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

    strict-transport-security is set on all 183 HTML pages.

  • OKClickjacking protection

    x-frame-options is set on all 183 HTML pages.

  • OKMIME sniffing protection

    x-content-type-options is set on all 183 HTML pages.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKKeys and secrets in page code

    No API keys, tokens or private keys were found in the sampled HTML and scripts.

  • OKExposed files and listings

    None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.

  • Not applicableCookie flags

    The crawl set no cookies, so there are no cookie flags to check.

  • Not applicableSensitive paths in robots.txt

    No robots.txt was fetched.

A passive review of what the crawl recorded: response headers, page and script contents and the URLs it found. It does not probe the site, test TLS settings or look for files that were not linked. Generated automatically; verify each finding against your own site before acting on it.

Sites scoring near www.puertomazatlan.com.mx

Their neighbours in the SEO rank table, which orders every scanned site by health score.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

This report was produced by the DIY SEO Hub Site Spider crawling www.puertomazatlan.com.mx from its pages as published, the way a search engine does. It shows summary figures only.

Own www.puertomazatlan.com.mx?

  • Claim this site to manage the listing, hide it from the public lists, or keep it.
  • Want it gone instead? Ask through the support form or e-mail support@diyseohub.com, naming www.puertomazatlan.com.mx. Removal needs no account and no proof of purchase.