Website review, no card needed

golrang.com logo

golrang.com website review

Visit site (opens in a new tab)Reviewed 27 October 202637 issues · 89 checks

This review found 37 issues worth fixing on golrang.com, 14 of them high impact, across 89 checks. The most urgent: font display. 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
2.0 s1.5 sMay 9Oct 241.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.9 s
May 16, 20261.9 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20261.8 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
92 ms83 msMay 9Oct 2489 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202690 ms
May 16, 202690 ms
May 23, 202689 ms
May 30, 202688 ms
Jun 6, 202687 ms
Jun 13, 202686 ms
Jun 20, 202686 ms
Jun 27, 202687 ms
Jul 4, 202688 ms
Jul 11, 202688 ms
Jul 18, 202688 ms
Jul 25, 202686 ms
Aug 1, 202684 ms
Aug 8, 202685 ms
Aug 15, 202685 ms
Aug 22, 202685 ms
Aug 29, 202687 ms
Sep 5, 202688 ms
Sep 12, 202688 ms
Sep 19, 202688 ms
Sep 26, 202687 ms
Oct 3, 202689 ms
Oct 10, 202689 ms
Oct 17, 202691 ms
Oct 24, 202689 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 golrang.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. golrang.com at 2.5 s2.5 s
  2. golrang.com at 5.0 s5.0 s
  3. golrang.com at 7.6 s7.6 s
  4. golrang.com at 10.1 s10.1 s
  5. golrang.com at 12.6 s12.6 s
  6. golrang.com at 15.1 s15.1 s
  7. golrang.com at 17.6 s17.6 s
  8. golrang.com at 20.1 s20.1 s

Speed

5 to fix78
  • Font display

    3.0 s

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

  • Render-blocking requests

    2.6 s

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

  • Improve image delivery

    2.4 MB

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

  • Mobile performance score: 78

    78/100

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

  • Reduce unused JavaScript

    450 ms · 100 KiB

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

  • Reduce unused CSS

    150 ms · 47 KiB

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

  • Minify CSS

    150 ms · 3 KiB

    3 KiB could be saved by minifying CSS.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Tag Manager and samandehi.ir), adding 140 KiB and 95 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 90 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    48 KiB

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

  • Legacy JavaScript

    7 KiB

    Polyfills for old browsers add 7 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.

2 checks passed
  • Main-thread work: 0.9 s

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

  • Server response: 189 ms

    189 ms

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

Core Web Vitals

4 to fix100
  • Speed Index: 15.4 s

    15.4 s

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

  • Largest Contentful Paint: 3.3 s

    3.3 s

    Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “گروه صنعتی گلرنگ با هدف توسعه تعامل و شبکه‌سازی با کارجویان…”. Most of its time is element render delay (6.4 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.

  • Time to Interactive: 4.4 s

    4.4 s

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

8 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: 2.1 s

    2.1 s

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

  • Real-user INP: 87 ms

    87 ms

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

  • Real-user CLS: 0.09

    0.09

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 481 ms

    481 ms

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

  • Cumulative Layout Shift: 0.085

    0.085

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

  • Total Blocking Time: 20 ms

    20 ms

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

Images and page weight

2 to fix60
  • Page weight: 4.8 MB in 101 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 101 requests on a phone: images 4.3 MB (86), scripts 235 KiB (6) and fonts 157 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    122 KiB

    1 image is downloaded at several times the size a phone draws it, for example Slider14040211.jpg at 1,904 px wide, shown at 390 px. Resized copies would save about 122 KiB.

  • 1 image in older formats

    1 image (196 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 1.4 g of CO₂ per visit

    1.36 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

13 to fixGoogle 7382
  • Input buttons must have discernible text (1 element)

    Input buttons must have discernible text: 1 element on the page fails this check, rated critical by axe-core.

  • Interactive controls must not be nested (3 elements)

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

  • 2 tap targets too small

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

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 25 images without alt text

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

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

  • Headings should not be empty (21 elements)

    Headings should not be empty: 21 elements on the page fail this check, rated minor by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Alternative text of images should not be repeated as text (3 elements)

    Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 41 automated accessibility rules passed

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

SEO

4 to fixGoogle 8387
  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 23 links with vague text

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

  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://golrang.com/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 132 internal links, 7 external

    The homepage links to 132 pages on golrang.com and 7 external pages.

5 checks passed
  • Meta description: 97 characters

    Your meta description is 97 characters: “«گروه صنعتی گلرنگ» یک مجموعه‌ اقتصادی پویاست که در زمینه‌های گوناگون سرمایه‌گذاری، فعالیت می‌کند.”.

  • One H1 headline

    Your main headline reads: “حضور گروه صنعتی گلرنگ در هشتمین نمایشگاه کار ایران”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “گروه صنعتی گلرنگ | Golrang Industrial Group”.

  • Structured data in place

    Structured data found: Organization.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

100
  • No llms.txt

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

  • Organization data: 4 of 6 facts

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

Other pages

1 to fix95
  • 1 page without a meta description

    https://golrang.com/contents/page/chart has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages with very little text

    https://golrang.com/Contents/news-detail/jobfair, https://golrang.com/Contents/news-detail/iran-cosmetica-1405, https://golrang.com/Contents/news-detail/opening-1405, https://golrang.com/Contents/news-detail/fazlicenter, https://golrang.com/Contents/news-detail/rahafarin-11 and https://golrang.com/Contents/news-detail/samin-1404 and 9 others 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.

  • 1 page slow to respond

    https://golrang.com/Contents/news-detail/fazlicenter took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 66 found) and read each the way a search engine does.

6 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 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

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://logo.samandehi.ir/logo.aspx?id=111153&p=nbpdnbpdnbpdnbpdujynqfti.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Bootstrap's tooltips require Popper.js (https://popper.js.org/)”.

2 checks passed
  • Tap targets are thumb-sized

    39 of 44 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix43
  • 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.

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

  • Only about 13 words

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

  • 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
  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 4 cookies set on arrival

    4

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

  • 2 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics
Hosting
Golrang System Co

Company

Founded
1960
Headquarters
Tehran

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on golrang.com, including 9 speed issues, 4 SEO issues and 5 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