kingofboards.com website review

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

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

Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.

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

About 105 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 files are served with short cache lifetimes, so returning visitors download them again (84 KiB).

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Bing Ads and others), adding 333 KiB and 141 ms of main-thread time.

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

Polyfills for old browsers add 6 KiB JavaScript that modern phones do not need.

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

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

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

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

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

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

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.

Your homepage downloads 2.6 MB in 286 requests on a phone: other files 1.3 MB (227), scripts 730 KiB (27) and images 340 KiB (22). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Electric-Skateboard_1024x1024.jpg at 800 px wide, shown at 167 px. Resized copies would save about 34 KiB.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

Contentinfo 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 contentinfo 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 on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

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

Your title is only 14 characters: “King Of Boards”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is 240 characters; Google truncates after about 160, so the end of your pitch is cut.

3 links have no real href, so search engines can't follow them.

The homepage links to 34 pages on kingofboards.com and 5 external pages.

There is no https://kingofboards.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://kingofboards.com/collections/completes and https://kingofboards.com/collections/street-cruisers have no meta description, so Google writes the search snippet from whatever text it finds.

https://kingofboards.com/collections/completes and https://kingofboards.com/collections/street-cruisers have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=25043411&Ver=2&mid=eb3193f8-f07a-4f0a-8e5f-e94cbaa76847&bo=1&sid=0bb76b90db6811f1936f7126994840a5&vid=0bb7bf70db6811f1a7fad16cb9ed1cbc&vids=1&msclkid=N&pi=918639831&lg.

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

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

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

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel and Microsoft Ads (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 9 cookies (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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.