plyconvanlines.com website review

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

Google Tag Manager costs a phone 1.1 s of main-thread work and 1.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Google Tag Manager, YouTube and Facebook and others), adding 2.4 MB and 2.0 s of main-thread time.

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

YouTube costs a phone 626 ms of main-thread work and 965 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.

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

5 images could be 166 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

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

Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Scripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.

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

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

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

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

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

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

Your homepage downloads 3.4 MB in 100 requests on a phone: scripts 2.4 MB (31), images 486 KiB (22) and fonts 308 KiB (9). Under 2 MB keeps phones on slow connections fast.

plycon_plycar_logo_2024-5c768193.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image (33 KiB) is 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.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (5 elements).

The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

Google's crawler is blocked from indexing this page.

Your title is only 21 characters: “Plycon Transportation”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 27 characters: “Plycon Transportation Group”. 70 to 160 characters is enough to sell the click.

There are 3 <h1> headlines (“#1 National Provider For Residential Moving Servi…”, “#1 National Provider For Residential Moving Servi…” and “QUICK QUOTE ESTIMATE”). One clear main headline is easier for people and search engines.

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

Open Graph is missing og:description, so shared links fall back to guesses.

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

The homepage links to 77 pages on plyconvanlines.com and 23 external pages.

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.

There is no https://plycongroup.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.

https://plycongroup.com/contact, https://plycongroup.com/services, https://plycongroup.com/residential-moving, https://plycongroup.com/warehousing-and-consolidation, https://plycongroup.com/packing-crating and https://plycongroup.com/white-glove-delivery and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://plycongroup.com/resources/moving-guide and https://plycongroup.com/news all use the title “Plycon Group”. Search engines can't tell which page to show for a search, so each competes with the others.

https://plycongroup.com/white-glove-delivery, https://plycongroup.com/resources/checklists and https://plycongroup.com/news have no meta description, so Google writes the search snippet from whatever text it finds.

https://plycongroup.com/services and https://plycongroup.com/news have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

3 errors were logged to the browser console while the page loaded, for example “Unexpected token '<'”.

6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 851 words of visible text.

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

Opening the homepage sets 10 cookies, 3 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.