Website review, no card needed
geoff.no website review
Visit site (opens in a new tab)Reviewed 21 October 202629 issues · 79 checks
This review found 29 issues worth fixing on geoff.no, 7 of them high impact, across 79 checks. The most urgent: page weight: 21.5 MB in 71 requests. 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
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 748 ms |
| May 9, 2026 | 740 ms |
| May 16, 2026 | 688 ms |
| May 23, 2026 | 679 ms |
| May 30, 2026 | 768 ms |
| Jun 6, 2026 | 775 ms |
| Jun 13, 2026 | 798 ms |
| Jun 20, 2026 | 831 ms |
| Jun 27, 2026 | 801 ms |
| Jul 4, 2026 | 841 ms |
| Jul 11, 2026 | 958 ms |
| Jul 18, 2026 | 954 ms |
| Jul 25, 2026 | 875 ms |
| Aug 1, 2026 | 841 ms |
| Aug 8, 2026 | 800 ms |
| Aug 15, 2026 | 783 ms |
| Aug 22, 2026 | 835 ms |
| Aug 29, 2026 | 835 ms |
| Sep 5, 2026 | 803 ms |
| Sep 12, 2026 | 765 ms |
| Sep 19, 2026 | 744 ms |
| Sep 26, 2026 | 741 ms |
| Oct 3, 2026 | 740 ms |
| Oct 10, 2026 | 763 ms |
| Oct 17, 2026 | 750 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 77 ms |
| May 9, 2026 | 80 ms |
| May 16, 2026 | 77 ms |
| May 23, 2026 | 79 ms |
| May 30, 2026 | 79 ms |
| Jun 6, 2026 | 80 ms |
| Jun 13, 2026 | 86 ms |
| Jun 20, 2026 | 87 ms |
| Jun 27, 2026 | 90 ms |
| Jul 4, 2026 | 90 ms |
| Jul 11, 2026 | 82 ms |
| Jul 18, 2026 | 79 ms |
| Jul 25, 2026 | 82 ms |
| Aug 1, 2026 | 88 ms |
| Aug 8, 2026 | 89 ms |
| Aug 15, 2026 | 94 ms |
| Aug 22, 2026 | 83 ms |
| Aug 29, 2026 | 79 ms |
| Sep 5, 2026 | 77 ms |
| Sep 12, 2026 | 73 ms |
| Sep 19, 2026 | 75 ms |
| Sep 26, 2026 | 75 ms |
| Oct 3, 2026 | 77 ms |
| Oct 10, 2026 | 79 ms |
| Oct 17, 2026 | 80 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
Speed
Use efficient cache lifetimes
450 ms · 11.5 MB5 files are served with short cache lifetimes, so returning visitors download them again (11.5 MB).
Improve image delivery
150 ms · 2.5 MB7 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (website-files.com, Google Tag Manager and cloudfront.net and others), adding 21.0 MB and 204 ms of main-thread time.
website-files.com adds 98 ms
98 mswebsite-files.com costs a phone 98 ms of main-thread work and 20.8 MB 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.
Mobile performance score: 73
73/100Your mobile performance score is 73 (desktop: 71). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
850 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 299 ms. During a long task the page ignores taps.
Reduce unused JavaScript
212 KiBAbout 212 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
18 KiBAbout 18 KiB of CSS is downloaded but never applied on this page.
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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 362 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.2 s
6.2 sYour largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 8.2 s
8.2 sThe page becomes fully interactive after 8.2 s. Good is under 3.8 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 77 ms to 80 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.7 s to 0.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: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 78 ms
78 msReal visitors wait 78 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Speed Index: 3.2 s
3.2 sVisually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 145 ms
145 msScripts block the page for only 145 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 21.5 MB in 71 requests
21.5 MBYour homepage downloads 21.5 MB in 71 requests on a phone: media 11.4 MB (2), images 9.2 MB (32) and scripts 552 KiB (14). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (26 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 6.1 g of CO₂ per visit
6.09 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.09 g of CO₂e: 730.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Form elements must have labels (3 elements)
Form elements must have labels: 3 elements on the page fail this check, rated critical by axe-core.
24 text elements with low contrast
24 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 (35 elements)
All page content should be contained by landmarks: 35 elements on the page fail this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 28 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 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 short (22 characters)
Your title is only 22 characters: “Golden Energy Offshore”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.geoff.no/sitemap.xml, so Google discovers your pages only by following links.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
69 internal links, 6 external
The homepage links to 69 pages on geoff.no and 6 external pages.
2 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “A fully integrated shipowner and operator of modern and high spec offshore service vessel for the global O&G and renewa…”.
robots.txt in place
robots.txt is in place.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.geoff.no/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,252 words), so crawlers that don't run JavaScript still read it.
Other pages
9 pages without a meta description
https://www.geoff.no/chartering, https://www.geoff.no/investors-geos, https://www.geoff.no/contact, https://www.geoff.no/our-fleet, https://www.geoff.no/career and https://www.geoff.no/qhse and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 32 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
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”.
2 checks passed
Tap targets are thumb-sized
27 of 27 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 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.
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 695 words of copy
The homepage carries about 695 words of visible text.
6 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact”.
1 short form
A short form (3 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 36 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 6 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
2 trackers load before any consent
2Before 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
3Opening 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.
12 other companies contacted
Loading the homepage contacts 12 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 geoff.no, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Webflow
- 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 29 issues on geoff.no, including 11 speed issues, 7 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.