Website review, no card needed

ptsinar.com logo

ptsinar.com website review

Visit site (opens in a new tab)Reviewed 20 November 202633 issues · 77 checks

This review found 33 issues worth fixing on ptsinar.com, 9 of them high impact, across 77 checks. The most urgent: use efficient cache lifetimes. 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.8 s1.2 sMay 30Nov 141.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.6 s
Jun 6, 20261.7 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.5 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.6 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.5 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Oct 31, 20261.4 s
Nov 7, 20261.3 s
Nov 14, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
161 ms112 msMay 30Nov 14155 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026139 ms
Jun 6, 2026130 ms
Jun 13, 2026126 ms
Jun 20, 2026129 ms
Jun 27, 2026130 ms
Jul 4, 2026127 ms
Jul 11, 2026136 ms
Jul 18, 2026134 ms
Jul 25, 2026129 ms
Aug 1, 2026134 ms
Aug 8, 2026127 ms
Aug 15, 2026119 ms
Aug 22, 2026119 ms
Aug 29, 2026118 ms
Sep 5, 2026120 ms
Sep 12, 2026125 ms
Sep 19, 2026127 ms
Sep 26, 2026141 ms
Oct 3, 2026147 ms
Oct 10, 2026149 ms
Oct 17, 2026152 ms
Oct 24, 2026151 ms
Oct 31, 2026149 ms
Nov 7, 2026154 ms
Nov 14, 2026155 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 ptsinar.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix86
  • Use efficient cache lifetimes

    1.8 s · 2.9 MB

    48 files are served with short cache lifetimes, so returning visitors download them again (2.9 MB).

  • Render-blocking requests

    2.9 s

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

  • Mobile performance score: 86

    86/100

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

  • Improve image delivery

    781 KiB

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

  • Reduce unused CSS

    600 ms · 118 KiB

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

  • Reduce unused JavaScript

    300 ms · 386 KiB

    About 386 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 381 ms

    381 ms

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Google Analytics and others), adding 335 KiB and 383 ms of main-thread time.

  • 5 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 1.6 s

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

  • Server response: 216 ms

    216 ms

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

Core Web Vitals

5 to fix100
  • Speed Index: 6.0 s

    6.0 s

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

  • Time to Interactive: 6.5 s

    6.5 s

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • Total Blocking Time: 265 ms

    265 ms

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

  • 3 images without width and height

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

  • Tap response (INP) got 15% slower for real visitors

    +15%

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

9 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.3 s

    1.3 s

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

  • Real-user INP: 149 ms

    149 ms

    Real visitors wait 149 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: 1.2 s

    1.2 s

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

  • Real-user TTFB: 604 ms

    604 ms

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

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

    -21%

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

  • Largest Contentful Paint: 2.2 s

    2.2 s

    Your largest element renders in 2.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “The world's leading fabric manufacturer with 46 years of in…”.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix43
  • 5 images far larger than shown

    1.4 MB

    5 images are downloaded at several times the size a phone draws them, for example IMG_0598-1-scaled.jpg.webp at 2,560 px wide, shown at 390 px. Resized copies would save about 1.4 MB.

  • 1 image over 500 KB

    IMG_0598-1-scaled.jpg.webp weighs 722 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.3 MB in 60 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 60 requests on a phone: images 2.1 MB (23), scripts 813 KiB (19) and fonts 207 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    DJI_0528-edit-scaled.jpg.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).

  • 4 images below the first screen load straight away

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

  • About 0.9 g of CO₂ per visit

    0.93 g

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

5 to fixGoogle 8793
  • 4 buttons without a name

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

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

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

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

  • 4 links without text

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

2 checks passed
  • Every image has alt text

    All 43 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 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

4 to fixGoogle 9275
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (18 characters)

    Your title is only 18 characters: “Home - Sinar Group”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“<img class="light-logo w-[140px] md:w-[215px] eww…” and “<img class="light-logo w-[140px] md:w-[215px] eww…”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 34 internal links, 9 external

    The homepage links to 34 pages on ptsinar.com and 9 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://ptsinar.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

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

AI search readiness

100
  • No llms.txt

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

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

  • Text is in the HTML

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

Other pages

3 to fix83
  • 4 pages share 2 titles

    / and https://ptsinar.com/id all use the title “Home - Sinar Group”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages without a meta description

    https://ptsinar.com/about, https://ptsinar.com/products, https://ptsinar.com/contact, https://ptsinar.com/career, https://ptsinar.com/news and https://ptsinar.com/id and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://ptsinar.com/products, whose canonical is https://ptsinar.com/products/interior. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 20 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.

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 5 small tap targets

    5 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

    The homepage carries about 313 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

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.

  • 3 cookies set on arrival

    3

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

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

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 ptsinar.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 | Google Tag Manager
Hosting
OVHcloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on ptsinar.com, including 12 speed issues, 4 SEO issues 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