Website review, no card needed

vascorlogistics.com logo

vascorlogistics.com website review

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

This review found 40 issues worth fixing on vascorlogistics.com, 16 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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.3 sMay 9Oct 242.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.7 s
May 16, 20262.4 s
May 23, 20262.5 s
May 30, 20262.5 s
Jun 6, 20262.4 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.9 s
Jul 4, 20263.0 s
Jul 11, 20262.8 s
Jul 18, 20263.0 s
Jul 25, 20262.6 s
Aug 1, 20262.5 s
Aug 8, 20262.7 s
Aug 15, 20262.6 s
Aug 22, 20263.0 s
Aug 29, 20262.8 s
Sep 5, 20262.7 s
Sep 12, 20262.7 s
Sep 19, 20262.7 s
Sep 26, 20262.9 s
Oct 3, 20262.8 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
186 ms74 msMay 9Oct 17155 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026146 ms
May 16, 2026149 ms
May 23, 2026157 ms
May 30, 2026152 ms
Jun 6, 2026135 ms
Jun 13, 2026108 ms
Jun 20, 2026104 ms
Jun 27, 202687 ms
Jul 4, 2026104 ms
Jul 11, 2026121 ms
Jul 18, 2026111 ms
Jul 25, 2026112 ms
Aug 1, 2026104 ms
Aug 8, 2026104 ms
Aug 15, 2026111 ms
Aug 22, 2026116 ms
Aug 29, 2026124 ms
Sep 5, 2026113 ms
Sep 12, 2026119 ms
Sep 19, 2026140 ms
Sep 26, 2026160 ms
Oct 3, 2026173 ms
Oct 10, 2026171 ms
Oct 17, 2026155 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 vascorlogistics.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. vascorlogistics.com at 0.7 s0.7 s
  2. vascorlogistics.com at 1.5 s1.5 s
  3. vascorlogistics.com at 2.2 s2.2 s
  4. vascorlogistics.com at 3.0 s3.0 s
  5. vascorlogistics.com at 3.7 s3.7 s
  6. vascorlogistics.com at 4.5 s4.5 s
  7. vascorlogistics.com at 5.2 s5.2 s
  8. vascorlogistics.com at 6.0 s6.0 s

Speed

10 to fix55
  • Reduce unused JavaScript

    5.2 s · 988 KiB

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

  • Improve image delivery

    3.3 s · 884 KiB

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

  • Use efficient cache lifetimes

    1.4 s · 211 KiB

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

  • Mobile performance score: 55

    55/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google CDN and Google Maps and others), adding 1.9 MB and 676 ms of main-thread time.

  • Reduce unused CSS

    450 ms · 159 KiB

    About 159 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.

  • Render-blocking requests

    600 ms

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

  • YouTube adds 308 ms

    308 ms

    YouTube costs a phone 308 ms of main-thread work and 977 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 118 ms

    118 ms

    Google CDN costs a phone 118 ms of main-thread work and 351 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 Maps adds 103 ms

    103 ms

    Google Maps costs a phone 103 ms of main-thread work and 393 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.

  • 7 long tasks on the main thread

    7 long tasks block the main thread while loading, the longest for 108 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.

2 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 28 ms

    28 ms

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

Core Web Vitals

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

  • First Contentful Paint: 10.5 s

    10.5 s

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

  • Largest Contentful Paint: 21.2 s

    21.2 s

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

  • Speed Index: 14.1 s

    14.1 s

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

  • Time to Interactive: 22.3 s

    22.3 s

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

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

  • 7 images without width and height

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

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

    +11%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

5 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 144 ms

    144 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Total Blocking Time: 79 ms

    79 ms

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

  • Cumulative Layout Shift: 0.005

    0.005

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

Images and page weight

1 to fix70
  • Page weight: 12.4 MB in 117 requests

    12.4 MB

    Your homepage downloads 12.4 MB in 117 requests on a phone: media 8.6 MB (1), scripts 1.8 MB (33) and images 1.6 MB (21). Under 2 MB keeps phones on slow connections fast.

  • About 3.5 g of CO₂ per visit

    3.51 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.51 g of CO₂e: 421.7 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

7 to fixGoogle 8188
  • Elements must only use permitted ARIA attributes (15 elements)

    Elements must only use permitted ARIA attributes: 15 elements on the page fail this check, rated serious by axe-core.

  • 6 text elements with low contrast

    6 text elements don'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.

  • 23 images without alt text

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

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

    All page content should be contained by landmarks: 11 elements on the page fail 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.

  • 20 links without text

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

1 checks passed
  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 7 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 7776
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (23 characters)

    Your title is only 23 characters: “Home - VASCOR Logistics”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 3 H1 headlines

    There are 3 <h1> headlines (“39 +”, “8921510 +” and “33616438 +”). One clear main headline is easier for people and search engines.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 27 internal links, 7 external

    The homepage links to 27 pages on vascorlogistics.com and 7 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://vascorlogistics.com/.

  • Structured data in place

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

  • XML sitemap found

    Your XML sitemap is reachable at https://vascorlogistics.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • 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://vascorlogistics.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.

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 (610 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 2 pages share a title

    / and https://vascorlogistics.com/es all use the title “Home - VASCOR Logistics”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://vascorlogistics.com/about-vascor, https://vascorlogistics.com/inbound-logistics, https://vascorlogistics.com/finished-vehicle-logistics, https://vascorlogistics.com/technology, https://vascorlogistics.com/careers and https://vascorlogistics.com/newsroom and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

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

  • 15 internal pages checked

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

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

  • 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

3 to fixGoogle 6985
  • 5 third-party cookies

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

  • 3 small tap targets

    3 of 10 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: net::ERR_FAILED”.

  • 1 low-resolution image

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

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Only about 220 words

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage has 5 calls to action, for example “Contact Us”, “LEARN MORE” and “contact us”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 4 cookies set on arrival

    4

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

  • 20 other companies contacted

    Loading the homepage contacts 20 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 vascorlogistics.com, 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
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on vascorlogistics.com, including 17 speed issues, 4 SEO issues 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