Website review, no card needed

ptsgi.com logo

ptsgi.com website review

Visit site (opens in a new tab)Reviewed 30 October 202624 issues · 77 checks

This review found 24 issues worth fixing on ptsgi.com, 6 of them high impact, across 77 checks. The most urgent: 1 text element with low contrast. 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
4.1 s2.1 sMay 9Oct 242.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.9 s
May 16, 20263.2 s
May 23, 20262.4 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20263.0 s
Jul 4, 20263.0 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20262.7 s
Aug 1, 20262.7 s
Aug 8, 20262.6 s
Aug 15, 20262.8 s
Aug 22, 20262.8 s
Aug 29, 20263.2 s
Sep 5, 20263.6 s
Sep 12, 20263.2 s
Sep 19, 20262.9 s
Sep 26, 20262.8 s
Oct 3, 20262.7 s
Oct 10, 20262.6 s
Oct 17, 20262.6 s
Oct 24, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
228 ms109 msMay 9Oct 24126 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026134 ms
May 16, 2026144 ms
May 23, 2026145 ms
May 30, 2026147 ms
Jun 6, 2026152 ms
Jun 13, 2026184 ms
Jun 20, 2026189 ms
Jun 27, 2026209 ms
Jul 4, 2026214 ms
Jul 11, 2026181 ms
Jul 18, 2026175 ms
Jul 25, 2026144 ms
Aug 1, 2026123 ms
Aug 8, 2026126 ms
Aug 15, 2026130 ms
Aug 22, 2026140 ms
Aug 29, 2026145 ms
Sep 5, 2026146 ms
Sep 12, 2026176 ms
Sep 19, 2026179 ms
Sep 26, 2026194 ms
Oct 3, 2026196 ms
Oct 10, 2026179 ms
Oct 17, 2026171 ms
Oct 24, 2026126 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 ptsgi.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ptsgi.com at 0.6 s0.6 s
  2. ptsgi.com at 1.3 s1.3 s
  3. ptsgi.com at 1.9 s1.9 s
  4. ptsgi.com at 2.5 s2.5 s
  5. ptsgi.com at 3.1 s3.1 s
  6. ptsgi.com at 3.8 s3.8 s
  7. ptsgi.com at 4.4 s4.4 s
  8. ptsgi.com at 5.0 s5.0 s

Speed

7 to fix82
  • Mobile performance score: 82

    82/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, openai.com and pstatic.net and others), adding 1.5 MB and 774 ms of main-thread time.

  • Google Tag Manager adds 698 ms

    698 ms

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

  • Use efficient cache lifetimes

    532 KiB

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

  • 7 long tasks on the main thread

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

  • Main-thread work: 2.5 s

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

  • Google Fonts adds 0 ms

    0 ms

    Google Fonts costs a phone 0 ms of main-thread work and 980 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 JavaScript

    214 KiB

    About 214 KiB of JavaScript is downloaded but never used on this page.

  • Improve image delivery

    171 KiB

    2 images could be 171 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    131 KiB

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

  • Legacy JavaScript

    15 KiB

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

  • 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: 133 ms

    133 ms

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

Core Web Vitals

2 to fix100
  • Time to Interactive: 11.5 s

    11.5 s

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

  • Total Blocking Time: 720 ms

    720 ms

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

  • Tap response (INP) held steady for real visitors

    +7%

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

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: 1.0 s

    1.0 s

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

  • Real-user INP: 91 ms

    91 ms

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

  • Real-user CLS: 0.05

    0.05

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 696 ms

    696 ms

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

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

    -28%

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

  • Speed Index: 2.9 s

    2.9 s

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

  • Cumulative Layout Shift: 0.034

    0.034

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

  • First Contentful Paint: 1.0 s

    1.0 s

    The first text or image appears after 1.0 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 1.0 s

    1.0 s

    Your largest element renders in 1.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “獲得 ISO 9001 / ISO 17100 / ISO 27001 認證”.

Images and page weight

1 to fix85
  • Page weight: 2.2 MB in 73 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 73 requests on a phone: fonts 1.1 MB (30), scripts 663 KiB (15) and images 203 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (256 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.

  • About 0.6 g of CO₂ per visit

    0.62 g

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

2 checks passed
  • 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

4 to fixGoogle 7090
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 27 images without alt text

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

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

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

  • Zoom is disabled

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

  • Headings skip levels

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

1 checks passed
  • 27 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 32 WCAG 2.2 A/AA and best-practice rules on the phone render: 27 passed and 5 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 9296
  • Structured data has 1 problem

    Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 1 problem, for example “BreadcrumbList: itemListElement is an empty list”.

  • 126 internal links, 1 external

    The homepage links to 126 pages on ptsgi.com and 1 external page.

7 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “統一數位翻譯(PTSGI.com)累積50多年的翻譯資源管理經驗,至今在全球已網羅11,267名翻譯人才,為全球之冠。為了提供世界級的專業翻譯公司,本公司採用GTAIS智慧系統結合AI大數據智能軟體,透過大數據的分析管理,提供全球高效率及…”.

  • One H1 headline

    Your main headline reads: “亞洲最大多語服務翻譯公司”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “亞洲最大翻譯公司,各類型文件翻譯,專業翻譯服務 | PTSGI.com”.

  • Canonical URL set

    The canonical URL is https://www.ptsgi.com/zhtw/.

  • 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.ptsgi.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

  • Opted out of AI training for 3 crawlers

    robots.txt blocks GPTBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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.

  • Organization data: 4 of 6 facts

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

Other pages

4 to fix81
  • 2 pages share a title

    https://www.ptsgi.com/en and https://www.ptsgi.com/nl all use the title “Top Translation Company in Asia | Professional Translation Services”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.ptsgi.com/zhtw/about-us and https://www.ptsgi.com/zhtw/join-us have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.ptsgi.com/en and https://www.ptsgi.com/nl use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://www.ptsgi.com/ja and https://www.ptsgi.com/zhtw/join-us have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://www.ptsgi.com/zhhk, https://www.ptsgi.com/zhtw/about-us, https://www.ptsgi.com/zhtw/certifications and https://www.ptsgi.com/zhtw/join-us 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 55 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    13 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot set properties of null (setting 'value')”.

2 checks passed
  • Tap targets are thumb-sized

    8 of 9 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Only about 103 words

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

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

2 checks passed
  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 14 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
Google Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on ptsgi.com, including 9 speed issues, 1 SEO issue and 3 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