Website review, no card needed

3glogistics.com logo

3glogistics.com website review

Visit site (opens in a new tab)Reviewed 19 October 202622 issues · 73 checks

This review found 22 issues worth fixing on 3glogistics.com, 7 of them high impact, across 73 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

Full-page screenshot of 3glogistics.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 3glogistics.com at 0.4 s0.4 s
  2. 3glogistics.com at 0.8 s0.8 s
  3. 3glogistics.com at 1.1 s1.1 s
  4. 3glogistics.com at 1.5 s1.5 s
  5. 3glogistics.com at 1.9 s1.9 s
  6. 3glogistics.com at 2.3 s2.3 s
  7. 3glogistics.com at 2.6 s2.6 s
  8. 3glogistics.com at 3.0 s3.0 s

Speed

4 to fix69
  • Render-blocking requests

    2.7 s

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

  • Reduce unused JavaScript

    1.4 s · 243 KiB

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

  • Mobile performance score: 69

    69/100

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

  • Font display

    750 ms

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Cookiebot and Google Fonts and others), adding 332 KiB and 320 ms of main-thread time.

  • Use efficient cache lifetimes

    150 ms · 33 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (33 KiB).

  • 2 long tasks on the main thread

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

  • Reduce unused CSS

    24 KiB

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

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

2 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 275 ms

    275 ms

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

Core Web Vitals

4 to fix71
  • Largest Contentful Paint: 5.7 s

    5.7 s

    Your largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”. Most of its time is element render delay (2.3 s).

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Speed Index: 5.1 s

    5.1 s

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

  • Time to Interactive: 5.7 s

    5.7 s

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

  • Not enough real-visitor data yet

    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.

2 checks passed
  • Total Blocking Time: 97 ms

    97 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 3.5 MB in 114 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 114 requests on a phone: media 2.4 MB (1), scripts 526 KiB (43) and fonts 364 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    1.01 g

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

5 to fixGoogle 9493
  • [role="img"] and [role="image"] elements must have alternative text (23 elements)

    [role="img"] and [role="image"] elements must have alternative text: 23 elements on the page fail this check, rated serious by axe-core.

  • 2 text elements with low contrast

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

  • 49 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: 49 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9294
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 6 links with vague text

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

  • 43 internal links, 12 external

    The homepage links to 43 pages on 3glogistics.com and 12 external pages.

7 checks passed
  • Meta description: 118 characters

    Your meta description is 118 characters: “3G Logistics Pte Ltd offers reliable Manpower Supply in Singapore, providing skilled workforce for various industries.”.

  • One H1 headline

    Your main headline reads: “3G Logistics Pte Ltd”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “3G Logistics Pte Ltd - Manpower Supply in Singapore”.

  • Canonical URL set

    The canonical URL is https://3glogistics.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://3glogistics.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://3glogistics.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 (452 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 2 pages share a title

    https://3glogistics.com/vision-values/corporate-overview and https://3glogistics.com/corporate-overview all use the title “Corporate Overview - 3G Logistics Pte Ltd.”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages share a meta description

    https://3glogistics.com/vision-values/corporate-overview, https://3glogistics.com/corporate-overview, https://3glogistics.com/management-team, https://3glogistics.com/sustainability, https://3glogistics.com/careers and https://3glogistics.com/contact use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://3glogistics.com/vision-values/corporate-overview, whose canonical is https://3glogistics.com/corporate-overview. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 8 pages slow to respond

    https://3glogistics.com/vision-values/corporate-overview, https://3glogistics.com/corporate-overview, https://3glogistics.com/management-team, https://3glogistics.com/sustainability, https://3glogistics.com/service/manpower-solutions and https://3glogistics.com/service/delivery and 2 others took over 3 s to send their HTML from our server.

  • 11 internal pages checked

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

5 checks passed
  • Linked pages load

    All 11 pages we checked loaded without an error.

  • Every page has a meta description

    All 11 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 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_TUNNEL_CONNECTION_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    12 of 13 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • Local business without LocalBusiness data

    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.

  • No opening hours

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

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

    The homepage carries about 386 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us Now”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Contact”, “LEARN MORE” and “GET IN TOUCH NOW”.

  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and “30 + Clients”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 6 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 3glogistics.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
Framework
jQuery
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 22 issues on 3glogistics.com, including 8 speed issues, 2 SEO issues and 1 conversion gap. 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