Website review, no card needed

1laser.com logo

1laser.com website review

Visit site (opens in a new tab)Reviewed 27 October 202626 issues · 103 checks

This review found 26 issues worth fixing on 1laser.com, 8 of them high impact, across 103 checks. The most urgent: 12 images over 500 KB. 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
1.2 s788 msMay 9Oct 24836 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.2 s
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.0 s
Aug 15, 20261.0 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.0 s
Sep 26, 2026977 ms
Oct 3, 2026954 ms
Oct 10, 2026897 ms
Oct 17, 2026863 ms
Oct 24, 2026836 ms
Real-visitor tap response (INP)75th percentile, phones
168 ms115 msMay 9Oct 24146 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026121 ms
May 16, 2026123 ms
May 23, 2026140 ms
May 30, 2026140 ms
Jun 6, 2026138 ms
Jun 13, 2026139 ms
Jun 20, 2026135 ms
Jun 27, 2026137 ms
Jul 4, 2026136 ms
Jul 11, 2026134 ms
Jul 18, 2026129 ms
Jul 25, 2026129 ms
Aug 1, 2026134 ms
Aug 8, 2026137 ms
Aug 15, 2026137 ms
Aug 22, 2026136 ms
Aug 29, 2026136 ms
Sep 5, 2026136 ms
Sep 12, 2026137 ms
Sep 19, 2026146 ms
Sep 26, 2026153 ms
Oct 3, 2026162 ms
Oct 10, 2026154 ms
Oct 17, 2026154 ms
Oct 24, 2026146 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 1laser.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 1laser.com at 0.4 s0.4 s
  2. 1laser.com at 0.9 s0.9 s
  3. 1laser.com at 1.3 s1.3 s
  4. 1laser.com at 1.7 s1.7 s
  5. 1laser.com at 2.2 s2.2 s
  6. 1laser.com at 2.6 s2.6 s
  7. 1laser.com at 3.1 s3.1 s
  8. 1laser.com at 3.5 s3.5 s

1laser.com does not allow embedding, so this is Google's rendering of the page.

Speed

3 to fix92
  • Improve image delivery

    1.6 MB

    30 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 2,289 HTML elements

    The page has 2,289 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • bonloyalty.com adds 0 ms

    0 ms

    bonloyalty.com costs a phone 0 ms of main-thread work and 330 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, cevoid.com and Klaviyo and others), adding 610 KiB and 3 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 55 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    12 KiB

    About 12 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    8 KiB

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

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

3 checks passed
  • Mobile performance score: 92

    92/100

    Your mobile performance score is 92 (desktop: 99). That is in Google's “good” band (90 and up).

  • Main-thread work: 0.9 s

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

  • Server response: 23 ms

    23 ms

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

Core Web Vitals

3 to fix100
  • Tap response (INP) got 23% slower for real visitors

    +23%

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Largest Contentful Paint: 2.7 s

    2.7 s

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

11 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 0.8 s

    0.8 s

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

  • Real-user INP: 121 ms

    121 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 632 ms

    632 ms

    Real visitors wait 632 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 25% faster for real visitors

    -25%

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

  • Speed Index: 2.7 s

    2.7 s

    Visually, the page fills in at 2.7 s (Speed Index), inside the 3.4 s “good” threshold.

  • Time to Interactive: 2.7 s

    2.7 s

    The page is fully interactive after 2.7 s.

  • Cumulative Layout Shift: 0.001

    0.001

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

5 to fix14
  • 12 images over 500 KB

    12 images weigh 13.4 MB together. On a phone connection a single image that size takes seconds.

  • Page weight: 7.0 MB in 142 requests

    7.0 MB

    Your homepage downloads 7.0 MB in 142 requests on a phone: images 6.0 MB (58), scripts 728 KiB (47) and HTML 135 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 40 images far larger than shown

    4.7 MB

    40 images are downloaded at several times the size a phone draws them, for example 02-product-photo-wall-panel.webp at 1,200 px wide, shown at 348 px. Resized copies would save about 4.7 MB.

  • 40 images in older formats

    40 images (18.9 MB) 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.

  • An image on the first screen is lazy-loaded

    02-product-photo-wall-panel.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).

  • About 2.0 g of CO₂ per visit

    2.00 g

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

Accessibility

7 to fixGoogle 8591
  • 3 buttons without a name

    3 buttons have no accessible name, so screen readers announce just “button”.

  • 9 text elements with low contrast

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

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

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

  • 4 links without text

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

  • 2 form fields without a label

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 136 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

1 to fixGoogle 9295
  • Meta description is long (165 characters)

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

  • 96 internal links, 11 external

    The homepage links to 96 pages on 1laser.com and 11 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Engrave the Future”.

  • Title: 31 characters

    Your title is a healthy 31 characters: “OneLaser – Make Better With One”.

  • Canonical URL set

    The canonical URL is https://www.1laser.com/.

  • Structured data in place

    Structured data found: LocalBusiness, Organization 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://www.1laser.com/sitemap.xml.

AI search readiness

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,287 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes /llms.txt (48 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 2 pages without a meta description

    /collections/all and /policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    /collections/all, /policies/shipping-policy, /collections/laser-engraving-cutting-marking-machines, /products/onelaser-xrf-desktop-laser-machine, /products/cobra-8-90w-co2-laser-engraver-cutter and /products/cobra-10-100w-co2-laser-engraver-cutter and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    /policies/shipping-policy and /collections/laser-engraving-cutting-marking-machines 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.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • 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

1 to fixGoogle 10084
  • 3 broken images

    3 images failed to load on a phone, for example https://www.1laser.com/.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    92 of 93 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (1laser.com).

  • Valid certificate (78 days left)

    The certificate from Let's Encrypt · YE1 verifies for 1laser.com and is valid for another 78 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://1laser.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 49 links work

    All 49 links checked from your homepage (40 internal, 9 external) answered without errors; 2 did not answer within 5 s.

Domain and trust

  • DNSSEC is off

    1laser.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

3 checks passed
  • Domain is 27 years old

    27 years

    1laser.com was registered in May 1999 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.

  • Certificate issuers are restricted

    CAA records allow only pki.goog, globalsign.com, ssl.com and letsencrypt.org to issue certificates for 1laser.com, so a mis-issued certificate from anyone else is refused.

  • Registered until May 2028

    1laser.com is registered until May 2028.

Content and conversion

2 to fix81
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

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

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

  • About 1,314 words of copy

    The homepage carries about 1,314 words of visible text.

6 checks passed
  • 14 calls to action

    The homepage has 14 calls to action, for example “Get a Quote”, “Join Community” and “Contact”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 5 testimonial or review blocks and 1 trust badge.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Email authentication

1 to fix70
  • DMARC is monitor-only (p=none)

    DMARC is set to p=none, so mail pretending to be 1laser.com is still delivered. Add a report address, check the reports, then move to quarantine.

  • Email authentication score: 70/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

2 checks passed
  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:mailgun.org ~all CNAME”.

  • DKIM signing found

    A DKIM key is published (selector “smtp”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (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.

  • 6 cookies set on arrival

    6

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

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

Upkeep, stack and company

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

Framework
jQuery
E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on 1laser.com, including 6 speed issues, 1 SEO issue and 2 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