Website review, no card needed
duanebartelsband.com website review
Visit site (opens in a new tab)Reviewed 20 November 202636 issues · 80 checks
This review found 36 issues worth fixing on duanebartelsband.com, 10 of them high impact, across 80 checks. The most urgent: unlabelled dropdowns. 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
70CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
750 ms · 195 KiB24 files are served with short cache lifetimes, so returning visitors download them again (195 KiB).
Improve image delivery
750 ms · 149 KiB2 images could be 149 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
Reduce unused JavaScript
610 ms · 101 KiBAbout 101 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 610 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Cloudflare and others), adding 581 KiB and 503 ms of main-thread time.
Render-blocking requests
300 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Google Tag Manager adds 271 ms
271 msGoogle Tag Manager costs a phone 271 ms of main-thread work and 196 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.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
Legacy JavaScript
200 ms · 43 KiBPolyfills for old browsers add 43 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Reduce unused CSS
150 ms · 43 KiBAbout 43 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.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 177 ms. During a long task the page ignores taps.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 465 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.5 s
8.5 sYour largest element takes 8.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “BOS5000 :: Pusat Yöre Tekstil Online Berbasis AI Terbaik 20…”.
Time to Interactive: 8.5 s
8.5 sThe page becomes fully interactive after 8.5 s. Good is under 3.8 s.
Speed Index: 4.9 s
4.9 sVisually, the page fills in at 4.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Total Blocking Time: 274 ms
274 msScripts block taps and scrolling for 274 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
1 image in older formats
1 image (208 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 0.3 g of CO₂ per visit
0.26 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.26 g of CO₂e: 30.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 923 KiB in 72 requests
923 KiBYour homepage downloads 923 KiB in 72 requests on a phone: scripts 455 KiB (33), images 238 KiB (13) and fonts 135 KiB (5). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Unlabelled dropdowns
2 dropdowns have no label.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
12 tap targets too small
12 tap targets are too small or too close together to hit reliably with a finger.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
12 images without alt text
12 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (22 elements)
All page content should be contained by landmarks: 22 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.
8 form fields without a label
8 form fields have no label, so screen readers announce an empty box and autofill guesses.
5 links without text
5 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.
1 checks passed
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“BOS5000 :: Pusat Yöre Tekstil Online Berbasis AI …” and “BOS5000 :: Pusat Yöre Tekstil Online Berbasis AI …”). One clear main headline is easier for people and search engines.
Structured data has 3 problems
Structured data found (FAQPage, Product and WebSite) but with 3 problems, for example “ld+json block 2 is not valid JSON (Bad control character in string literal in JSON at position )”.
No XML sitemap
No XML sitemap at https://www.yoretekstil.com/sitemap.xml, so Google discovers your pages only by following links.
43 internal links, 3 external
The homepage links to 43 pages on duanebartelsband.com and 3 external pages.
5 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Nikmati pengalaman bermain modern di BOS5000, pusat permainan online berbasis AI 2026. Didukung teknologi pintar, siste…”.
Title: 61 characters
Your title is a healthy 61 characters: “BOS5000 :: Pusat Yöre Tekstil Online Berbasis AI Terbaik 2026”.
Canonical URL set
The canonical URL is https://www.yoretekstil.com/otantik-perdeler-1-1555.
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.
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.yoretekstil.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 (853 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages are broken
Your homepage links to https://www.yoretekstil.com/deposit and https://www.yoretekstil.com/info/privacy, which answer with an error. Visitors hit a dead end and search engines drop them.
2 pages share a title
https://www.yoretekstil.com/otantik-perdeler-1-1555 and https://www.yoretekstil.com/amp all use the title “BOS5000 :: Pusat Yöre Tekstil Online Berbasis AI Terbaik 2026”. Search engines can't tell which page to show for a search, so each competes with the others.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.yoretekstil.com/amp, whose canonical is https://www.yoretekstil.com/otantik-perdeler-1-1555. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.yoretekstil.com/amp has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.yoretekstil.com/amp has 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.
3 internal pages checked
We fetched 3 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Every page has a meta description
All 1 page that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 1 page that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://www.yoretekstil.com/static/img/icons/payment/paypal.png.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
12 of 14 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.
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.
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 479 words of copy
The homepage carries about 479 words of visible text.
4 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Sign up with Facebook”, “Sign up with Email” and “Contact”.
6 short forms
6 short forms (6 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and a star rating.
Analytics in place
Analytics detected: Google Analytics, Meta Pixel and Cloudflare Web Analytics.
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 Meta Pixel (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
13 other companies contacted
Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 duanebartelsband.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
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on duanebartelsband.com, including 13 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.