Website review, no card needed

gulfex.com logo

gulfex.com website review

Visit site (opens in a new tab)Reviewed 31 October 202658 issues · 100 checks

This review found 58 issues worth fixing on gulfex.com, 26 of them high impact, across 100 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
4.4 s2.5 sMay 9Oct 242.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.2 s
May 16, 20263.2 s
May 23, 20263.3 s
May 30, 20263.2 s
Jun 6, 20263.3 s
Jun 13, 20263.1 s
Jun 20, 20263.1 s
Jun 27, 20263.4 s
Jul 4, 20263.4 s
Jul 11, 20263.4 s
Jul 18, 20263.4 s
Jul 25, 20263.5 s
Aug 1, 20263.4 s
Aug 8, 20263.6 s
Aug 15, 20263.6 s
Aug 22, 20264.0 s
Aug 29, 20264.2 s
Sep 5, 20263.6 s
Sep 12, 20263.4 s
Sep 19, 20263.0 s
Sep 26, 20262.7 s
Oct 3, 20262.9 s
Oct 10, 20262.9 s
Oct 17, 20262.8 s
Oct 24, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
130 ms96 msMay 9Oct 24113 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026101 ms
May 16, 2026106 ms
May 23, 2026115 ms
May 30, 2026119 ms
Jun 6, 2026126 ms
Jun 13, 2026122 ms
Jun 20, 2026108 ms
Jun 27, 2026108 ms
Jul 4, 2026106 ms
Jul 11, 2026103 ms
Jul 18, 2026105 ms
Jul 25, 2026104 ms
Aug 1, 2026100 ms
Aug 8, 2026104 ms
Aug 15, 2026104 ms
Aug 22, 2026102 ms
Aug 29, 2026108 ms
Sep 5, 2026102 ms
Sep 12, 2026103 ms
Sep 19, 2026103 ms
Sep 26, 2026103 ms
Oct 3, 2026114 ms
Oct 10, 2026114 ms
Oct 17, 2026113 ms
Oct 24, 2026113 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 gulfex.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gulfex.com at 1.1 s1.1 s
  2. gulfex.com at 2.1 s2.1 s
  3. gulfex.com at 3.2 s3.2 s
  4. gulfex.com at 4.3 s4.3 s
  5. gulfex.com at 5.3 s5.3 s
  6. gulfex.com at 6.4 s6.4 s
  7. gulfex.com at 7.5 s7.5 s
  8. gulfex.com at 8.5 s8.5 s

Speed

12 to fix44
  • Use efficient cache lifetimes

    5.5 s · 8.7 MB

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

  • Reduce unused JavaScript

    2.9 s · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.

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

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

  • Google CDN adds 1.3 s

    1.3 s

    Google CDN costs a phone 1.3 s of main-thread work and 1.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 44

    44/100

    Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 5.2 s

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Tag Manager and others), adding 2.4 MB and 1.7 s of main-thread time.

  • Improve image delivery

    1.5 MB

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

  • Reduce unused CSS

    460 ms · 95 KiB

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

  • 20 long tasks on the main thread

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

  • Cloudflare CDN adds 18 ms

    18 ms

    Cloudflare CDN costs a phone 18 ms of main-thread work and 300 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.

  • Minify JavaScript

    9 KiB

    9 KiB could be saved by minifying JavaScript.

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

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 213 ms

    213 ms

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

Core Web Vitals

10 to fix67
  • 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.

  • Largest Contentful Paint: 23.4 s

    23.4 s

    Your largest element takes 23.4 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 enhance your browsing experience, serve p…”.

  • Time to Interactive: 45.1 s

    45.1 s

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

  • Speed Index: 10.6 s

    10.6 s

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

  • Total Blocking Time: 775 ms

    775 ms

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • First Contentful Paint: 2.5 s

    2.5 s

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

  • 13 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +9%

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

4 checks passed
  • Real-user INP: 116 ms

    116 ms

    Real visitors wait 116 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.

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

    -11%

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

  • Cumulative Layout Shift: 0.024

    0.024

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

Images and page weight

5 to fix18
  • Page weight: 12.2 MB in 173 requests

    12.2 MB

    Your homepage downloads 12.2 MB in 173 requests on a phone: images 8.4 MB (108), scripts 2.2 MB (34) and other files 702 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 2.7 MB together. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    538 KiB

    4 images are downloaded at several times the size a phone draws them, for example SliderMain21.png at 1,508 px wide, shown at 346 px. Resized copies would save about 538 KiB.

  • 26 images in older formats

    26 images (5.9 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.

  • 14 images below the first screen load straight away

    14 images further down the page (2.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.5 g of CO₂ per visit

    3.46 g

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

Accessibility

14 to fixGoogle 6682
  • Certain ARIA roles must be contained by particular parents (5 elements)

    Certain ARIA roles must be contained by particular parents: 5 elements on the page fail this check, rated critical by axe-core.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Orphan list items

    Some list items are not inside a list.

  • ARIA input fields must have an accessible name (2 elements)

    ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 44 images without alt text

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

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

    All page content should be contained by landmarks: 21 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.

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

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 9 links without text

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

  • 7 form fields without a label

    7 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

5 to fixGoogle 7769
  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (21 characters)

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

  • No social preview image

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

  • 3 links with vague text

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

  • 91 internal links, 17 external

    The homepage links to 91 pages on gulfex.com and 17 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://gulfex.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://gulfex.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://gulfex.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 (1,346 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 2 pages share a title

    https://gulfex.com/about-us and https://gulfex.com/index.php/about-us all use the title “About Us - Gulf Extrusion”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://gulfex.com/contact-us, https://gulfex.com/about-us, https://gulfex.com/index.php/about-us, https://gulfex.com/products, https://gulfex.com/product_category/architectural and https://gulfex.com/product_category/automotive and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 links to non-canonical URLs

    Your homepage links to 15 pages by a URL that isn't their canonical one, for example https://gulfex.com/contact-us, whose canonical is https://gulfex.com/?page_id=24. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 5 pages slow to respond

    https://gulfex.com/index.php/about-us, https://gulfex.com/products, https://gulfex.com/gulfservice/extrusion, https://gulfex.com/gulfservice/crimping and https://gulfex.com/gulfservice/anodizing took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 to fixGoogle 8562
  • 2 broken images

    2 images failed to load on a phone, for example https://gulfex.com/wp-content/uploads/2023/07/close.png.

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 6 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 4 low-resolution images

    4 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • 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 map 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.

  • About 377 words of copy

    The homepage carries about 377 words of visible text.

7 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us”, “Download” and “Subscribe”.

  • 5 short forms

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

  • Social proof on the page

    Social proof on the homepage: 33 testimonial or review blocks and 39 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 13 phone links and 4 email links.

  • Phone number on the homepage

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 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). 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.

  • 7 other companies contacted

    Loading the homepage contacts 7 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 gulfex.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
Hosting
Emirates Internet

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 58 issues on gulfex.com, including 22 speed issues, 5 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