Website review, no card needed
duraline.com website review
Visit site (opens in a new tab)Reviewed 30 October 202635 issues · 84 checks
This review found 35 issues worth fixing on duraline.com, 12 of them high impact, across 84 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
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.7 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 102 ms |
| May 16, 2026 | 102 ms |
| May 23, 2026 | 101 ms |
| May 30, 2026 | 104 ms |
| Jun 6, 2026 | 103 ms |
| Jun 13, 2026 | 105 ms |
| Jun 20, 2026 | 110 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 103 ms |
| Jul 18, 2026 | 101 ms |
| Jul 25, 2026 | 104 ms |
| Aug 1, 2026 | 105 ms |
| Aug 8, 2026 | 103 ms |
| Aug 15, 2026 | 101 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 95 ms |
| Sep 5, 2026 | 97 ms |
| Sep 12, 2026 | 95 ms |
| Sep 19, 2026 | 97 ms |
| Sep 26, 2026 | 95 ms |
| Oct 3, 2026 | 94 ms |
| Oct 10, 2026 | 95 ms |
| Oct 17, 2026 | 93 ms |
| Oct 24, 2026 | 95 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
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
Use efficient cache lifetimes
3.6 s · 494 KiB13 files are served with short cache lifetimes, so returning visitors download them again (494 KiB).
Reduce unused JavaScript
2.3 s · 497 KiBAbout 497 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Render-blocking requests
1.8 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Reduce unused CSS
960 ms · 142 KiBAbout 142 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 960 ms faster on a phone.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
150 ms · 521 KiB8 images could be 521 KiB 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.
7 third-party services on the page
7 third-party services load with your homepage (Cookiebot, Google Tag Manager and azure.com and others), adding 556 KiB and 248 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 59 ms. During a long task the page ignores taps.
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: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 316 ms of it running JavaScript. That is comfortably low.
Server response: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
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.
Largest Contentful Paint: 10.5 s
10.5 sYour largest element takes 10.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “<h1>Dura-Line Test Track: Global Capability; Local Agility<…”.
Time to Interactive: 10.7 s
10.7 sThe page becomes fully interactive after 10.7 s. Good is under 3.8 s.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Speed Index: 5.4 s
5.4 sVisually, the page fills in at 5.4 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 102 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 103 ms
103 msReal visitors wait 103 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Real-user TTFB: 669 ms
669 msReal visitors wait 669 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.073
0.073The layout barely moves while loading (CLS 0.073, good is under 0.1).
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: 2.0 MB in 53 requests
2.0 MBYour homepage downloads 2.0 MB in 53 requests on a phone: images 903 KiB (22), scripts 863 KiB (16) and stylesheets 159 KiB (4). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
139 KiB3 images are downloaded at several times the size a phone draws them, for example digital-tools-teaser-2.png at 1,014 px wide, shown at 330 px. Resized copies would save about 139 KiB.
6 images below the first screen load straight away
6 images further down the page (409 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.57 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.57 g of CO₂e: 68.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
10 tap targets too small
10 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
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.
10 images without alt text
10 images have no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
15 links without text
15 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
34 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: 34 passed and 9 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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 (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.
2 links crawlers can't follow
2 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.
172 internal links, 21 external
The homepage links to 172 pages on duraline.com and 21 external pages.
5 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Our lives depend on clear, consistent, reliable communication. Discover how Dura-Line High, a global manufacturer of HD…”.
One H1 headline
Your main headline reads: “Dura-Line Test Track: Global Capability; Local Agility”.
Title: 37 characters
Your title is a healthy 37 characters: “Creating what connects us | Dura-Line”.
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://www.duraline.com/sitemap.xml.
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.duraline.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,218 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages share a title
https://www.duraline.com/micro-technology, https://www.duraline.com/all-products/462, https://www.duraline.com/all-products/463, https://www.duraline.com/all-products/164 and https://www.duraline.com/all-products/2074 all use the title “MicroTechnology | Dura-Line”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://www.duraline.com/my-duraline, https://www.duraline.com/about-us/Ethics-Compliance, https://www.duraline.com/about-us/quality, https://www.duraline.com/contact and https://www.duraline.com/region-language-switcher have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages share a meta description
https://www.duraline.com/micro-technology, https://www.duraline.com/all-products/462, https://www.duraline.com/all-products/463, https://www.duraline.com/all-products/164 and https://www.duraline.com/all-products/2074 use the same meta description. A description written for each page earns more clicks.
2 pages with very little text
https://www.duraline.com/my-duraline and https://www.duraline.com/region-language-switcher 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 101 found) and read each the way a search engine does.
5 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.
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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
10 of 11 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 579 words of copy
The homepage carries about 579 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More”.
6 calls to action
The homepage has 6 calls to action, for example “Contact” and “Learn More”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo and 9 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
10 other companies contacted
Loading the homepage contacts 10 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 duraline.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- Episerver
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on duraline.com, including 12 speed issues and 5 SEO issues. 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.