Website review, no card needed

1-to-all.com logo

1-to-all.com website review

Visit site (opens in a new tab)Reviewed 3 November 202647 issues · 93 checks

This review found 47 issues worth fixing on 1-to-all.com, 15 of them high impact, across 93 checks. The most urgent: render-blocking requests. 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.4 s2.7 sMay 16Oct 313.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.1 s
May 23, 20263.0 s
May 30, 20262.9 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20263.0 s
Jun 27, 20263.1 s
Jul 4, 20263.2 s
Jul 11, 20263.3 s
Jul 18, 20263.2 s
Jul 25, 20263.1 s
Aug 1, 20263.0 s
Aug 8, 20263.0 s
Aug 15, 20263.1 s
Aug 22, 20263.1 s
Aug 29, 20263.1 s
Sep 5, 20263.0 s
Sep 12, 20263.1 s
Sep 19, 20263.0 s
Sep 26, 20263.1 s
Oct 3, 20263.0 s
Oct 10, 20263.1 s
Oct 17, 20263.3 s
Oct 24, 20263.1 s
Oct 31, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
193 ms122 msMay 16Oct 31130 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026143 ms
May 23, 2026148 ms
May 30, 2026135 ms
Jun 6, 2026130 ms
Jun 13, 2026157 ms
Jun 20, 2026154 ms
Jun 27, 2026163 ms
Jul 4, 2026170 ms
Jul 11, 2026163 ms
Jul 18, 2026172 ms
Jul 25, 2026172 ms
Aug 1, 2026172 ms
Aug 8, 2026185 ms
Aug 15, 2026173 ms
Aug 22, 2026167 ms
Aug 29, 2026153 ms
Sep 5, 2026149 ms
Sep 12, 2026145 ms
Sep 19, 2026166 ms
Sep 26, 2026183 ms
Oct 3, 2026183 ms
Oct 10, 2026178 ms
Oct 17, 2026170 ms
Oct 24, 2026157 ms
Oct 31, 2026130 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 1-to-all.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 1-to-all.com at 0.7 s0.7 s
  2. 1-to-all.com at 1.4 s1.4 s
  3. 1-to-all.com at 2.2 s2.2 s
  4. 1-to-all.com at 2.9 s2.9 s
  5. 1-to-all.com at 3.6 s3.6 s
  6. 1-to-all.com at 4.3 s4.3 s
  7. 1-to-all.com at 5.0 s5.0 s
  8. 1-to-all.com at 5.8 s5.8 s

Speed

15 to fix20
  • Render-blocking requests

    11.1 s

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

  • Reduce unused JavaScript

    3.8 s · 1.8 MB

    About 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.

  • Mobile performance score: 20

    20/100

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

  • Main-thread work: 6.7 s

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

  • 8 third-party services on the page

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

  • Improve image delivery

    1.0 MB

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

  • Squarespace adds 869 ms

    869 ms

    Squarespace costs a phone 869 ms of main-thread work and 1.5 MB 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 Tag Manager adds 611 ms

    611 ms

    Google Tag Manager costs a phone 611 ms of main-thread work and 750 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.

  • Reduce unused CSS

    300 ms · 205 KiB

    About 205 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Legacy JavaScript

    350 ms · 91 KiB

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

  • Use efficient cache lifetimes

    426 KiB

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

  • 20 long tasks on the main thread

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

  • 1,835 HTML elements

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

  • JSDelivr CDN adds 58 ms

    58 ms

    JSDelivr CDN costs a phone 58 ms of main-thread work and 1,018 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.

  • sqspcdn.com adds 119 ms

    119 ms

    sqspcdn.com costs a phone 119 ms of main-thread work and 354 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.

  • Minify JavaScript

    150 ms · 39 KiB

    39 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

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

  • Duplicated JavaScript

    38 KiB

    38 KiB JavaScript is shipped twice across bundles.

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

1 checks passed
  • Server response: 105 ms

    105 ms

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

Core Web Vitals

12 to fix33
  • 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: 11.8 s

    11.8 s

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

  • Largest Contentful Paint: 11.8 s

    11.8 s

    Your largest element takes 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Telecom/Mobile Operator อันดับ 4 ของประเทศไทย”.

  • Speed Index: 16.2 s

    16.2 s

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

  • Time to Interactive: 43.5 s

    43.5 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Real-user CLS: 0.25

    0.25

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • Cumulative Layout Shift: 0.225

    0.225

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

1 checks passed
  • Real-user INP: 130 ms

    130 ms

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

Images and page weight

3 to fix53
  • Page weight: 11.4 MB in 189 requests

    11.4 MB

    Your homepage downloads 11.4 MB in 189 requests on a phone: images 5.2 MB (36), scripts 3.5 MB (74) and other files 2.0 MB (35). Under 2 MB keeps phones on slow connections fast.

  • 7 images below the first screen load straight away

    7 images further down the page (609 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    136 KiB

    1 image is downloaded at several times the size a phone draws it, for example iso-9001-2015-png-7.jpg at 1,985 px wide, shown at 87 px. Resized copies would save about 136 KiB.

  • About 3.2 g of CO₂ per visit

    3.24 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

7 to fixGoogle 8690
  • 19 text elements with low contrast

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

  • 12 tap targets too small

    12 tap targets are too small or too close together to hit reliably with a finger.

  • Interactive controls must not be nested (10 elements)

    Interactive controls must not be nested: 10 elements on the page fail this check, rated serious by axe-core.

  • Frames without titles

    2 frames have no title, so screen-reader users cannot tell what they contain.

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

    All page content should be contained by landmarks: 34 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.

  • 17 links without text

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 51 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

4 to fixGoogle 9282
  • Title is short (8 characters)

    Your title is only 8 characters: “1-TO-ALL”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 11 H1 headlines

    There are 11 <h1> headlines (“Telecom/Mobile Operator อันดับ 4 ของประเทศไทย”, “Digital Transformation at SCALE” and “OUR SOLUTIONS”). One clear main headline is easier for people and search engines.

  • Structured data has 2 problems

    Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/5d688d3af945320001b…”.

  • 5 links with vague text

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

  • 114 internal links, 29 external

    The homepage links to 114 pages on 1-to-all.com and 29 external pages.

5 checks passed
  • Meta description: 108 characters

    Your meta description is 108 characters: “No.1 Zoom and Microsoft 365 Solution ผู้นำด้าน Hybrid Working , Workplace Transformation, Future of Learning”.

  • Canonical URL set

    The canonical URL is https://www.1-to-all.com/.

  • 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.1-to-all.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing name, url, logo and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.1-to-all.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 (1,713 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.1-to-all.com/working-together is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 5 pages without a meta description

    https://www.1-to-all.com/products, https://www.1-to-all.com/news-update, https://www.1-to-all.com/blog, https://www.1-to-all.com/contact-us and https://www.1-to-all.com/zoom/video-webinar have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.1-to-all.com/news-update, https://www.1-to-all.com/blog and https://www.1-to-all.com/contact-us have 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 (of 49 found) 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

2 checks passed
  • Tap targets are thumb-sized

    60 of 63 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • 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 723 words of copy

    The homepage carries about 723 words of visible text.

9 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact us” and “Plans & Pricing”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Contact us”, “Plans & Pricing” and “Try ZOOM”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 5 testimonial or review blocks, 5 customer or partner logos, 5 trust badges and “Over 4,500 Customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    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.

  • 6 cookies set on arrival

    6

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

  • 26 other companies contacted

    Loading the homepage contacts 26 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 1-to-all.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2013.

Stack

CMS
Squarespace
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Squarespace

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on 1-to-all.com, including 27 speed issues and 4 SEO issues. 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