Website review, no card needed
sunflagsteel.com website review
Visit site (opens in a new tab)Reviewed 18 November 202638 issues · 65 checks
This review found 38 issues worth fixing on sunflagsteel.com, 20 of them high impact, across 65 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
62DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 5.4 s |
| Jun 6, 2026 | 5.4 s |
| Jun 13, 2026 | 5.4 s |
| Jun 20, 2026 | 5.6 s |
| Jun 27, 2026 | 5.8 s |
| Jul 4, 2026 | 5.7 s |
| Jul 11, 2026 | 5.7 s |
| Jul 18, 2026 | 5.7 s |
| Jul 25, 2026 | 5.8 s |
| Aug 1, 2026 | 5.9 s |
| Aug 8, 2026 | 5.7 s |
| Aug 15, 2026 | 5.7 s |
| Aug 22, 2026 | 5.7 s |
| Aug 29, 2026 | 5.7 s |
| Sep 5, 2026 | 6.0 s |
| Sep 12, 2026 | 5.9 s |
| Sep 19, 2026 | 6.0 s |
| Sep 26, 2026 | 6.0 s |
| Oct 3, 2026 | 5.9 s |
| Oct 10, 2026 | 5.9 s |
| Oct 17, 2026 | 5.5 s |
| Oct 24, 2026 | 5.3 s |
| Oct 31, 2026 | 5.1 s |
| Nov 7, 2026 | 5.1 s |
| Nov 14, 2026 | 5.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 131 ms |
| Jun 6, 2026 | 128 ms |
| Jun 13, 2026 | 131 ms |
| Jun 20, 2026 | 135 ms |
| Jun 27, 2026 | 133 ms |
| Jul 4, 2026 | 136 ms |
| Jul 11, 2026 | 137 ms |
| Jul 18, 2026 | 142 ms |
| Jul 25, 2026 | 143 ms |
| Aug 1, 2026 | 134 ms |
| Aug 8, 2026 | 129 ms |
| Aug 15, 2026 | 123 ms |
| Aug 22, 2026 | 127 ms |
| Aug 29, 2026 | 133 ms |
| Sep 5, 2026 | 134 ms |
| Sep 12, 2026 | 138 ms |
| Sep 19, 2026 | 134 ms |
| Sep 26, 2026 | 132 ms |
| Oct 3, 2026 | 128 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 118 ms |
| Oct 24, 2026 | 119 ms |
| Oct 31, 2026 | 125 ms |
| Nov 7, 2026 | 127 ms |
| Nov 14, 2026 | 132 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
1.8 s
3.6 s
5.5 s
7.3 s
9.1 s
10.9 s
12.8 s
14.6 s
Speed
Use efficient cache lifetimes
15.8 s · 6.5 MB111 files are served with short cache lifetimes, so returning visitors download them again (6.5 MB).
Render-blocking requests
14.8 s34 files block the first paint until they finish downloading. Deferring or inlining them could save about 14.8 s.
Reduce unused CSS
11.7 s · 2.0 MBAbout 2.0 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 11.7 s faster on a phone.
Reduce unused JavaScript
1.5 s · 340 KiBAbout 340 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Font display
1.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.0 s).
Mobile performance score: 33
33/100Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
2.5 MB18 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Document request latency
750 ms · 179 KiBThe HTML itself could arrive about 750 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
750 msReduce initial server response time. Google estimates savings of 750 ms on a phone.
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,718 HTML elements
The page has 1,718 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Server response: 850 ms
850 msYour server takes 850 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Minify CSS
210 ms · 30 KiB30 KiB could be saved by minifying CSS.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 54 ms. During a long task the page ignores taps.
1 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 87 KiB and 1 ms of main-thread time.
Minify JavaScript
8 KiB8 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.
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: 6.8 s
6.8 sReal visitors wait 6.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.68
0.68For real visitors the layout shifts by 0.68 (75th percentile). Good is under 0.1.
Real-user FCP: 6.3 s
6.3 sReal visitors see the first content after 6.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 4.2 s
4.2 sReal visitors wait 4.2 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 17.2 s
17.2 sThe first text or image appears after 17.2 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 26.5 s
26.5 sYour largest element takes 26.5 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.2 s
22.2 sVisually, the page fills in at 22.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 26.7 s
26.7 sThe page becomes fully interactive after 26.7 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.601
0.601The layout shifts by 0.601 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 131 ms to 132 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 5.4 s to 5.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 159 ms
159 msReal visitors wait 159 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 4 ms
4 msScripts block the page for only 4 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 7.0 MB in 119 requests
7.0 MBYour homepage downloads 7.0 MB in 119 requests on a phone: images 3.3 MB (33), stylesheets 2.1 MB (34) and scripts 931 KiB (45). Under 2 MB keeps phones on slow connections fast.
About 2.0 g of CO₂ per visit
1.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.97 g of CO₂e: 236.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
5 links without text
5 links have no text or label, so screen readers cannot say where they go.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (1 element).
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
Headings skip levels
Headings skip levels (h2 → h6, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.
Elements with role="none" or role="presentation" have conflicts
Elements with role="none" or role="presentation" have conflicts (2 elements).
1 checks passed
Every image has alt text
All 78 images in the HTML carry an alt attribute.
SEO
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 (12 characters)
Your title is only 12 characters: “Sunflagsteel”. 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 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://sunflagsteel.com/wp-sitemap.xml, so Google discovers your pages only by following links.
5 links crawlers can't follow
5 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
92 internal links, 17 external
The homepage links to 92 pages on sunflagsteel.com and 17 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://sunflagsteel.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
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.
1 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.
Other pages
Your server turned our page checks away
15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.
Best practices
1 console error
1 error was logged to the browser console during Google's test (“Failed to load resource: net::ERR_CONNECTION_FAILED”).
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: “0 + Clients”. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 913 words of copy
The homepage carries about 913 words of visible text.
2 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Custom Order Management” and “Contact Us”.
Direct contact links
Visitors can reach you directly: 0 phone links and 3 email links.
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 sunflagsteel.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2023.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Hosting
- GoDaddy
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on sunflagsteel.com, including 22 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.