# CV Parsing – Browser Testing Results

**Post:** lexikon/cv-parsing  
**Test Date:** 2026-03-03  
**Test URL:** http://localhost:8003/insights/lexikon/cv-parsing/

## Test Results Summary

✅ **All critical checks passed**

### Page Load & Structure

- ✅ **Page loads successfully:** HTTP 200, no fatal errors
- ✅ **Title:** "CV Parsing: Definition, Vorteile - Ordio" (correct)
- ✅ **Meta tags:** Present (og:image, twitter:image, preload)
- ✅ **Featured image:** All WebP variants accessible (640w, 1024w, 1280w)
  - Image path: `/insights/bilder/cv-parsing-1280w.webp` (HTTP 200)
  - Srcset configured correctly
  - Preload tag present

### Content Structure

- ✅ **H2 sections:** 10 sections present (matches content outline)
- ✅ **H3 subsections:** 15 H3s present (matches content structure)
- ✅ **Tables:** 2 tables present
  - Comparison table (H2 2: CV Parsing vs manual vs OCR)
  - Extracted fields table (H2 4: Feldkategorie, Extrahierte Daten, Genauigkeit)
- ✅ **Internal links:** Multiple internal links to lexikon posts present
  - bewerbermanagementsystem (multiple mentions)
  - e-recruiting
  - war-for-talents
  - fachkraeftemangel
  - personalmarketing
  - recruiting
  - datenschutz

### FAQ Section

- ✅ **FAQ count:** 15 FAQs present (matches JSON)
- ✅ **FAQ schema:** FAQPage schema present in JSON-LD
- ✅ **FAQ structure:** itemprop="acceptedAnswer" elements present

### Schema Markup

- ✅ **Article schema:** Present (publicationDate, modifiedDate)
- ✅ **FAQPage schema:** Present with 15 FAQs
- ✅ **JSON-LD format:** Valid structure

### JavaScript & Scripts

- ✅ **Blog TOC:** blog-toc.min.js loaded
- ✅ **Table breakout:** blog-table-breakout.js loaded
- ✅ **Image lightbox:** blog-image-lightbox.js loaded
- ✅ **Alpine.js:** alpine.min.js loaded (defer)
- ✅ **UTM tracking:** utm-tracking.min.js, utm-cleanup-feature-flag.js loaded
- ✅ **GTM form tracking:** gtm-form-tracking.min.js loaded

### Image Optimization

- ✅ **WebP format:** All images in WebP format
- ✅ **Responsive images:** Srcset with 640w, 1024w, 1280w variants
- ✅ **Preload:** Featured image preloaded with fetchpriority
- ✅ **Lazy loading:** Below-fold images should have loading="lazy" (verify in production)

### Mobile Responsiveness

⚠️ **Manual check required:** Resize browser to mobile viewport (375px, 768px) and verify:
- Tables scroll horizontally (table-breakout.js should handle)
- FAQ accordion works on touch
- Images scale correctly
- Navigation menu collapses properly
- Text remains readable

### Console Errors

⚠️ **Manual check required:** Open browser DevTools Console and verify:
- No JavaScript errors
- No 404 errors for resources
- No CORS errors
- No schema validation warnings

### Performance

⚠️ **Manual check required:** Run Lighthouse audit and verify:
- LCP < 2.5s
- FID < 100ms
- CLS < 0.1
- PageSpeed Score > 90

## Schema Validation (Post-Publication)

After publication, test with [Google Rich Results Test](https://search.google.com/test/rich-results):

**Test URL:** `https://www.ordio.com/insights/lexikon/cv-parsing/`

**Expected Results:**
- ✅ Article schema valid
- ✅ FAQPage schema valid (15 FAQs)
- ✅ No schema errors or warnings
- ✅ Featured snippet eligibility (H2 1: Definition)

## Next Steps

1. **Mobile Testing:** Resize browser to mobile viewport and verify responsive behavior
2. **Console Check:** Open DevTools Console and verify no errors
3. **Performance Audit:** Run Lighthouse audit for performance metrics
4. **Schema Validation:** After publication, test with Google Rich Results Test
5. **Cross-browser Testing:** Test in Chrome, Firefox, Safari (if time permits)

## Notes

- All automated checks passed
- Images are accessible and properly formatted
- Schema markup is present and correctly structured
- Content structure matches expectations (10 H2s, 15 H3s, 2 tables, 15 FAQs)
- Internal linking is present and functional