Website review, no card needed
goelscientific.com website review
Visit site (opens in a new tab)Reviewed 3 November 202644 issues · 90 checks
This review found 44 issues worth fixing on goelscientific.com, 24 of them high impact, across 90 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
73C- #87,301 of 117,602 reviewed websitesbeats 22%
- #54,889 of 66,923 online storesbeats 15%
- #1,649 of 2,700 WooCommerce storesbeats 33%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.0 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.8 s |
| Aug 29, 2026 | 4.0 s |
| Sep 5, 2026 | 4.0 s |
| Sep 12, 2026 | 4.1 s |
| Sep 19, 2026 | 4.6 s |
| Sep 26, 2026 | 4.6 s |
| Oct 3, 2026 | 4.7 s |
| Oct 10, 2026 | 4.6 s |
| Oct 17, 2026 | 4.9 s |
| Oct 24, 2026 | 5.3 s |
| Oct 31, 2026 | 5.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 106 ms |
| May 23, 2026 | 108 ms |
| May 30, 2026 | 113 ms |
| Jun 6, 2026 | 111 ms |
| Jun 13, 2026 | 113 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 113 ms |
| Aug 1, 2026 | 118 ms |
| Aug 8, 2026 | 124 ms |
| Aug 15, 2026 | 138 ms |
| Aug 22, 2026 | 124 ms |
| Aug 29, 2026 | 110 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 139 ms |
| Sep 19, 2026 | 168 ms |
| Sep 26, 2026 | 311 ms |
| Oct 3, 2026 | 311 ms |
| Oct 10, 2026 | 316 ms |
| Oct 17, 2026 | 324 ms |
| Oct 24, 2026 | 258 ms |
| Oct 31, 2026 | 145 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
How it loaded on a phone
2.4 s
4.8 s
7.1 s
9.5 s
11.9 s
14.3 s
16.6 s
19.0 s
Speed
Use efficient cache lifetimes
15.7 s · 7.2 MB160 files are served with short cache lifetimes, so returning visitors download them again (7.2 MB).
Improve image delivery
9.5 s · 3.0 MB14 images could be 3.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.5 s faster on a phone.
Render-blocking requests
6.2 s48 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.2 s.
Reduce unused JavaScript
3.0 s · 534 KiBAbout 534 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Reduce unused CSS
3.0 s · 451 KiBAbout 451 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Font display
3.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).
Main-thread work: 12.2 s
A phone's processor spends 12.2 s on main-thread work while loading, 5.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,093 HTML elements
The page has 3,093 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Clarity and cloudflare.com and others), adding 1.1 MB and 1.1 s of main-thread time.
Google Tag Manager adds 870 ms
870 msGoogle Tag Manager costs a phone 870 ms of main-thread work and 839 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 434 ms. During a long task the page ignores taps.
Minify CSS
300 ms · 34 KiB34 KiB could be saved by minifying CSS.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 438 ms
438 msYour server sent the HTML in 438 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user LCP: 5.0 s
5.0 sReal visitors wait 5.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.5 s
4.5 sReal visitors see the first content after 4.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.7 s
2.7 sReal visitors wait 2.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 29.3 s
29.3 sYour largest element takes 29.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 22.1 s
22.1 sVisually, the page fills in at 22.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 42.2 s
42.2 sThe page becomes fully interactive after 42.2 s. Good is under 3.8 s.
First Contentful Paint: 5.4 s
5.4 sThe first text or image appears after 5.4 s on a phone. Good is under 1.8 s.
Total Blocking Time: 924 ms
924 msScripts block taps and scrolling for 924 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 88% slower for real visitors
+88%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 106 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 62% slower for real visitors
+62%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.0 s to 5.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Real-user INP: 146 ms
146 msReal visitors wait 146 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.066
0.066The layout barely moves while loading (CLS 0.066, good is under 0.1).
Images and page weight
Page weight: 13.2 MB in 217 requests
13.2 MBYour homepage downloads 13.2 MB in 217 requests on a phone: images 5.7 MB (51), other files 4.2 MB (25) and scripts 1.3 MB (69). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
Robot-1.gif weighs 1.4 MB. On a phone connection a single image that size takes seconds.
2 images far larger than shown
689 KiB2 images are downloaded at several times the size a phone draws them, for example Robot-1.gif at 400 px wide, shown at 100 px. Resized copies would save about 689 KiB.
10 images in older formats
10 images (3.5 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
Industrial-Technical-Packages-1.png 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).
1 image below the first screen load straight away
1 image further down the page (47 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 3.8 g of CO₂ per visit
3.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.75 g of CO₂e: 450.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
17 text elements with low contrast
17 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
20 form fields without a label
20 form fields have no label, so screen readers announce an empty box and autofill guesses.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 88 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “Industrial Glass Process System Manufacturer India | Goel Scientific”.
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.
356 internal links, 17 external
The homepage links to 356 pages on goelscientific.com and 17 external pages.
6 checks passed
Meta description: 137 characters
Your meta description is 137 characters: “Goel Scientific Offer industrial glass systems, custom lab glassware, and turnkey process solutions for chemical indust…”.
Canonical URL set
The canonical URL is https://goelscientific.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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://goelscientific.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://goelscientific.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,827 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://goelscientific.com/career has no meta description, so Google writes the search snippet from whatever text it finds.
7 pages slow to respond
https://goelscientific.com/blog, https://goelscientific.com/career, https://goelscientific.com/about-us, https://goelscientific.com/product/advanced-glass-jacketed-reactor-with-pilot-horizontal-condenser, https://goelscientific.com/product/glass-lined-reactor-assembly and https://goelscientific.com/product/glass-reactor and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 123 found) and read each the way a search engine does.
6 checks passed
Linked pages load
7 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.
Titles are unique
Every page we checked has its own title.
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 7 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.
2 checks passed
Tap targets are thumb-sized
22 of 23 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 466 words of copy
The homepage carries about 466 words of visible text.
6 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Contact Us”, “Contact Goel Scientific Glass Works” and “Contact”.
7 short forms
7 short forms (6 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks and “over 2,800+ satisfied customers”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
15 other companies contacted
Loading the homepage contacts 15 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 goelscientific.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
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on goelscientific.com, including 25 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.