a.lup.dev favicon

a.lup.dev

https://a.lup.dev· First analyzed 14 Apr 2026· Updated 14 Apr 2026
Export
a.lup.dev
Desktop screenshot of a.lup.dev
Mobile screenshot of a.lup.dev
Mobile

Sponsored

Hosting Provider

hetzner.com

IP Address

188.245.98.145

Site Location

🇩🇪 Germanyvia ip

Server Location

🇩🇪 Nuremberg, Germany

ASN

AS24940

Organization

Hetzner

Server

Nginx

Performance

100

Core Web Vitals

Weight

First Contentful Paint
551 ms10%
Speed Index
716 ms10%
Largest Contentful Paint
25%
Total Blocking Time
0.0 ms30%
Cumulative Layout Shift
0.00025%
280 KB
19 requests

Image Optimization

Lazy LoadWebPResponsiveJetpack Photon (WordPress)
0–49
50–89
90–100

Architecture Stack

Monolithic
⚙️ SSR
WordPress
cms
Glassv1.0.0Custom
by Andrei Lupu
View Theme

Technology Stack

7 Technologies Detected

SEO Analysis

A84/100
27
5
0
Meta Tags9/15
Content8/12
Headings8/8
Technical23/25
E-E-A-T7/7
Images5/7
Links5/5
URL5/5
Social4/5
Freshness4/4
Mobile3/4
Indexability3/3
A
a.lup.deva.lup.dev

Homepage - Andrei Lupu

Andrei Lupu — backend dev, WordPress expert, and AI explorer. Writing about high-performance stacks and modern backend architectures.

Title Length22 chars

Recommended: 50-60 chars (~137px / 580px)

Description Length133 chars

Recommended: 120-160 chars

Issues (0)

    Crawlability

    Sitemap

    Type: index

    2 URLs

    2 sub-sitemaps

    robots.txt

    Local SEO

    Local Search Readiness

    16/100
    Poor
    5 12 1

    This site doesn't appear to be a local business. Local SEO signals are optional for non-local websites.

    Sponsored

    AI & LLM Readiness

    D53/100
    Bot Access
    20/25
    Machine Read.
    7/25
    Schema Data
    10/25
    Citation
    16/25

    AI Bot Access

    14/14 accessible
    AI Search
    OAI-SearchBot
    PerplexityBot
    Claude-SearchBot
    Gemini-Deep-Research
    DuckAssistBot
    Training
    GPTBot
    ClaudeBot
    Google-Extended
    Meta-ExternalAgent
    Bytespiderinfo
    Amazonbot
    Applebot-Extended
    CCBotinfo
    Fetch
    ChatGPT-User

    Machine Readability

    llms.txt
    llms-full.txt
    Semantic HTML
    Heading Hierarchy
    navheader/footer
    Text ratio:1%
    Words:289
    Token eff.:Too Short
    Sections/1K:20.8
    Depth:2/5

    Structured Data

    4 JSON-LD
    Person×1.3Organization×1.1WebSiteBreadcrumbListSearchAction

    Citation Readiness

    Opening Summary19w
    Descriptive Headingsavg 4.3w
    Canonical URL
    Open Graph3/3
    Twitter Card1/3
    Language Tag
    Publish Date
    Author Info
    Lists
    Tables
    TL;DR / Summary
    About Page Link
    Recommendations (8)
    AI readiness recommendation preview...

    Sponsored

    Accessibility

    WCAG 2.1 Compliance

    Evaluates how accessible your website is for users with disabilities, based on WCAG 2.1 guidelines. Checks images, forms, keyboard navigation, ARIA roles, and color contrast.
    A+
    91/100
    16
    Passed
    0
    Critical
    0
    Warnings
    Images & Alt Text
    20/20
    Checks if images have descriptive alt text for screen readers and visually impaired users.
    Semantic Structure
    20/20
    Evaluates proper use of HTML5 semantic elements (header, nav, main, footer) and heading hierarchy.
    Forms & Inputs
    15/15
    Verifies form fields have labels, error messages are clear, and inputs are properly associated.
    Color & Contrast
    15/15
    Tests text-to-background color contrast ratios against WCAG AA/AAA minimum requirements.
    Keyboard & Focus
    15/15
    Ensures all interactive elements are reachable and operable via keyboard (tab, enter, escape).
    ARIA & Roles
    6/15
    Checks correct use of WAI-ARIA attributes (roles, states, properties) for assistive technologies.

    Carbon Footprint

    SWDM v4 · Eco-Score

    Carbon emissions estimated using the Sustainable Web Design Model v4 (SWDM v4). Factors in data center, network, and device energy across new and returning visitors. Grade thresholds based on HTTP Archive percentiles.
    92/100
    A+
    28 mg
    CO₂e / view
    280.4 KB
    Page Weight
    90%
    Cleaner Than
    New Visitor
    32 mg
    vs
    Returning (cached)
    16 mg
    Annual (10K/mo)
    3.4 kg
    Emission Segments
    Data Center
    1 mg
    Network
    8 mg
    Device
    19 mg
    Resource Breakdown
    JavaScript
    20.8 KB
    Images
    129.8 KB
    CSS
    48.7 KB
    Fonts
    46.4 KB
    HTML
    26.1 KB
    Other
    8.6 KB
    Green Hosting Verified
    Hetzner Online GmbH
    GWF Verified
    2 recommendations
    • Carbon footprint recommendation preview...
    B

    Security Score

    76%Good
    Static / Informational

    HTTPS

    No WAF

    37d

    Certificate Details

    Type

    Domain Validated (DV)

    Certificate Authority

    Let's Encrypt

    Key Algorithm

    ECDSA (secp256r1) (256 bit)

    Signature

    ECDSA with SHA-384

    TLS Version

    TLSv1.3

    HTTP Protocol

    HTTP/2

    Valid From

    21.02.2026

    Valid Until

    22.05.2026

    Subject Alternative Names (1)

    a.lup.dev

    SHA-256 Fingerprint

    9C:B9:30:1B:AF:09:45:11:3D:75:5E:0F:11:64:27:1F:A4:5C:2C:1F...

    Recommendations

    Security recommendation preview

    HTTP Headers

    Developer Console

    content-encoding
    📦 Gzip(gzip)
    content-type
    text/html; charset=UTF-8
    date
    Tue, 14 Apr 2026 05:33:15 GMT
    link
    <https://a.lup.dev/wp-json/>; rel="https://api.w.org/", <htt...
    server
    nginx centminmod
    vary
    Accept-Encoding, accept, content-type
    Good Warning Issue

    Email Infrastructure

    Custom Mail Server

    Score

    0

    SPF
    DKIM
    DMARC

    Domain Information

    a.lup.dev

    DNSSEC
    Not Enabled

    Privacy & Compliance

    Cookie Consent Banner
    Privacy Policy
    Terms of Service

    Mobile Compatibility

    Viewport & Responsive Test

    Tests how well your website works on mobile devices. Checks viewport configuration, responsive layout, touch targets, font readability, and simulates rendering across different screen sizes.
    A
    81/100
    Mobile Friendly6 breakpoints
    Viewport Meta
    The viewport meta tag tells mobile browsers how to scale the page. Without it, mobile devices render at desktop width.
    Responsive Design
    Uses CSS media queries or flexible layouts to adapt content to different screen sizes automatically.
    Touch Icons
    Apple touch icons and favicons displayed when users add the site to their home screen on mobile devices.
    Readable Font Size
    Base font size should be at least 16px on mobile to ensure text is readable without zooming.
    Relative Units
    Using em, rem, %, or vw instead of fixed px values allows content to scale properly across screen sizes.
    No H-Scroll Risk
    No elements wider than the viewport that would cause horizontal scrolling on mobile devices.
    Tap Targets OK
    Interactive elements (buttons, links) are at least 48x48px with enough spacing to prevent accidental taps.
    No Fixed Widths
    No elements with fixed pixel widths that could overflow on smaller screens and break the layout.
    Viewport
    width=device-width, initial-scale=1
    1 recommendation
    • Mobile compatibility recommendation preview...

    Typography & Readability

    Space Grotesk + Manrope

    WCAG Partial
    77/100
    Readability
    /30
    19/30

    14px · LH 1.60

    Hierarchy
    /20
    20/20

    6.29x ratio · ✓ H1→H6

    WCAG
    /25
    18/25

    1.12:1 min contrast

    Performance
    /25
    20/25

    2 fonts · 3 req

    Heading Font

    Space Grotesk

    Sans88px

    Body Font

    Manrope

    Sans14px

    Contrast Ratio

    1.12:1

    9 issues

    Reading Comfort

    ~35 CPL

    Narrow lines
    88px
    h1
    32px
    h2
    40px
    h3
    14px
    p

    ⚠️ Small text: 14px may strain on mobile. Use ≥16px for WCAG compliance.

    ✅ Optimal line spacing: 1.60 ratio (ideal range 1.4–1.6).

    ⚠️ Partial contrast: 9 elements below WCAG AA threshold (min 1.1:1).

    ✅ Perfect heading hierarchy: Sequential h1→h2→h3 with single H1 — ideal for SEO & accessibility.

    ✅ Strong hierarchy: Headlines are 6.3x larger than body text.

    ✅ Modern fluid typography: clamp() with rem units ensures zoom accessibility (WCAG 1.4.4).

    Buy on MyFontsFluid Type (rem)Flesch 64

    Color Palette

    3 unique colors
    Light
    #f3f3f7
    Primary· 67%
    #e5e1f6
    Background· 26.3%
    #7385a9
    Secondary· 6.7%

    Business & Marketing Stack

    1 Tools Detected

    Growing

    Behavior Analytics

    1

    User behavior and product analytics

    1

    Categories

    1

    Total Tools

    0

    Enterprise

    0

    Mid-Market

    Assessment: Growing marketing technology adoption

    Sponsored

    Scripts & Styles

    9 Resources

    5
    Scripts
    4
    Styles
    1
    Async
    1
    Defer

    Top Script Sources

    a.lup.dev(3)googletagmanager.com(1)stats.wp.com(1)

    Website Identity

    Homepage - Andrei Lupu

    Andrei Lupu — backend dev, WordPress expert, and AI explorer. Writing about high-performance stacks and modern backend architectures.

    Location detected: 🇩🇪 Germanyvia ip
    en-US

    Sponsored

    Last analyzed: 14 Apr 2026 at 05:33

    AI-Powered Analysis

    Technical Deep Dive

    Executive Summary

    StackOptic's comprehensive analysis of a.lup.dev reveals a robust, developer-centric technical foundation, primarily built upon WordPress hosted by Hetzner in Germany. The site leverages Nginx as its web server, indicating a focus on performance and reliability. Frontend development is streamlined with Tailwind CSS, while user behavior tracking is handled by Google Analytics 4. Key strengths include advanced image optimization using Jetpack Photon, lazy loading, and WebP support, contributing to a commendable load time of 1033ms. However, the analysis also highlights critical areas for improvement, particularly regarding fundamental SEO elements like title and meta description tags, as well as comprehensive email security protocols such as SPF, DKIM, and DMARC.

    Technology Stack Deep Dive

    Frontend Technologies

    The frontend of a.lup.dev showcases a modern approach to web design and development, primarily driven by Tailwind CSS. This utility-first CSS framework allows developers to build custom designs directly in their HTML, emphasizing speed and maintainability. Its presence suggests a preference for rapid UI development and a highly customized aesthetic without the overhead of traditional, opinionated CSS frameworks. The absence of other major frontend JavaScript frameworks (like React, Vue, or Angular) implies that dynamic functionalities are either handled by WordPress's native capabilities, custom vanilla JavaScript, or are not a primary focus of the site's interactive elements. This choice can lead to leaner client-side code, potentially improving initial page load times and reducing JavaScript parsing overhead, though its impact on interactivity would depend on the site's specific features.

    Backend & Server Infrastructure

    At the core of a.lup.dev's backend and server infrastructure is Nginx, serving as the web server. Nginx is renowned for its high performance, stability, rich feature set, and low resource consumption, making it a popular choice for high-traffic websites and as a reverse proxy. Its selection over alternatives like Apache suggests an emphasis on efficient handling of concurrent connections and static content delivery. The server_software explicitly identifies Nginx, reinforcing its role in serving web content. This setup, combined with the underlying hosting provider, forms a solid, performant base for the WordPress application.

    Content Management & Frameworks

    a.lup.dev is powered by WordPress, a ubiquitous and highly flexible content management system (CMS). WordPress's presence indicates that the site likely benefits from its extensive ecosystem of themes, plugins, and user-friendly content authoring experience. While the specific WordPress version was not publicly exposed during the scan, its selection points to a platform chosen for its ease of use, scalability, and broad community support. Given the use of Tailwind CSS, it's probable that a custom WordPress theme has been developed or a highly customized off-the-shelf theme is in use, leveraging WordPress's templating capabilities in conjunction with modern CSS practices. The combination provides a powerful platform for content delivery while allowing for significant design flexibility.

    Hosting & Infrastructure Analysis

    Hosting Provider Profile

    a.lup.dev is hosted by Hetzner, a prominent German-based hosting provider known for its robust infrastructure, competitive pricing, and strong privacy stance. Hetzner is popular among developers and businesses seeking dedicated servers, cloud solutions, and colocation services, often favored for its performance and reliability in the European market. The choice of Hetzner suggests a preference for a provider that offers significant control over server environments and potentially higher performance at a reasonable cost, aligning with a technical audience's expectations. This provider is not typically associated with entry-level shared hosting, implying a more managed or self-managed server setup.

    CDN & Performance Infrastructure

    The scan data indicates that a.lup.dev is not utilizing a traditional Content Delivery Network (CDN) for its primary content delivery (is_cdn: false). However, it's important to note the detection of Jetpack Photon (WordPress) within the image optimization data. Jetpack Photon is a free CDN service specifically for images, provided by Automattic (the company behind WordPress.com and Jetpack). While not a full-site CDN, Photon significantly offloads image serving, caching them globally and resizing them on demand, which is a crucial performance optimization for image-heavy WordPress sites. The absence of a full CDN for other assets means that non-image content is served directly from the Hetzner server, potentially impacting load times for users geographically distant from Germany.

    Geographic & Network Analysis

    The server for a.lup.dev is located in Germany, as indicated by the hosting provider Hetzner. This geographic placement is ideal for users within Europe, offering lower latency and faster response times. For audiences outside Europe, particularly in North America or Asia, this could introduce higher latency, as data has to travel further. The absence of a comprehensive CDN means that network performance will be more directly tied to the physical distance between the user and the German server. The use of HTTP/2 is a positive, as it allows for multiplexing and server push, reducing the overhead of multiple requests over a single connection, which can help mitigate some latency issues.

    Security Assessment

    SSL/TLS Configuration

    a.lup.dev employs a valid SSL certificate issued by Let's Encrypt - E7, a widely trusted certificate authority providing free, automated, and open certificates. The certificate type is DV (Domain Validated), which confirms domain ownership. The key algorithm used is ECDSA (secp256r1), a modern and efficient elliptic curve cryptography algorithm that offers strong security with smaller key sizes and faster cryptographic operations compared to traditional RSA. The site also utilizes HTTP/2, which often works in conjunction with TLS to provide a more secure and performant connection. This indicates a commitment to securing data in transit and protecting user privacy. The tls_version data point was not publicly exposed during the scan, so the specific TLS protocol version in use (e.g., TLS 1.2 or 1.3) could not be determined.

    Security Headers Analysis

    Regarding security headers, the scan data indicates that HSTS (HTTP Strict Transport Security) is not explicitly enabled or was not publicly exposed during the scan. HSTS is a critical security mechanism that forces browsers to interact with the site using only HTTPS, preventing downgrade attacks and cookie hijacking. The absence of this data point suggests a potential area for improvement in bolstering the site's defense against certain web-based threats. Other important security headers like Content Security Policy (CSP), X-Frame-Options, and X-Content-Type-Options were not explicitly scanned for in this dataset, but their implementation is highly recommended for a robust security posture. The security_score data point was not publicly exposed during the scan.

    Overall Security Posture

    a.lup.dev demonstrates a foundational level of security with a valid Let's Encrypt ECDSA SSL certificate ensuring encrypted communications via HTTP/2. This is a strong starting point. However, the lack of explicit HSTS configuration is a notable gap that should be addressed to prevent protocol downgrade attacks. Furthermore, a comprehensive security strategy would typically involve implementing additional security headers and regularly auditing the WordPress installation for vulnerabilities, especially since the specific WordPress version was not detected. While the current setup provides basic encryption, a proactive approach to security headers would significantly enhance the site's overall resilience against common web exploits.

    SEO & Technical Health

    Meta Tags & Structure

    The scan reveals significant room for improvement in fundamental SEO elements. Both the title tag and meta description were not detected (null). These are critical for search engine visibility, user click-through rates from search results, and conveying the purpose of each page. Without a clear title, search engines may generate one, which might not be optimal, and the lack of a meta description means a generic snippet will likely be displayed. Addressing these omissions is paramount for improving organic search performance. The presence of a sitemap is a positive, aiding search engines in discovering and indexing content, but it cannot fully compensate for missing on-page meta information.

    Indexability & Crawlability

    a.lup.dev has a sitemap (has_sitemap: true), which is excellent for guiding search engines through the site's structure and ensuring all relevant pages are discoverable. However, the absence of a robots.txt file (has_robots_txt: false) is a critical oversight. While not having a robots.txt file means all content is implicitly allowed to be crawled, it also means there's no explicit mechanism to disallow specific sections or prevent excessive crawling, which can be useful for managing crawl budget and preventing indexing of non-essential pages. Best practice dictates having a robots.txt file, even if it's just an empty one or allows all, to provide explicit instructions to crawlers.

    Email Infrastructure & Domain

    The email security posture for a.lup.dev is a significant area of concern. The scan data indicates that SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail), and DMARC (Domain-based Message Authentication, Reporting, and Conformance) records are all absent (has_spf: false, has_dkim: false, has_dmarc: false). Consequently, the email_security_score is 0. This lack of email authentication makes the domain highly susceptible to email spoofing, phishing attacks, and can severely impact email deliverability, as legitimate emails from the domain may be flagged as spam by recipient servers. Implementing these protocols is crucial for protecting the domain's reputation and ensuring email integrity. The email_provider data point was not publicly exposed during the scan. Regarding domain information, the domain_age_days, creation_date, expiry_date, and registrar data points were not publicly exposed during the scan. DNSSEC is reported as false, meaning the domain's DNS records are not cryptographically signed, which could make it vulnerable to DNS cache poisoning attacks.

    Privacy & Compliance

    The privacy configuration of a.lup.dev shows several areas requiring attention. The site lacks a detected cookie consent platform (cookie_consent_platform: null) and a cookie banner (has_cookie_banner: false). This is a critical compliance issue, especially for websites serving users in regions with strict data privacy regulations like GDPR (Europe) or CCPA (California), which mandate explicit consent for non-essential cookies. The presence of Google Analytics for tracking (tracking_scripts: ["Google Analytics"]) further underscores the necessity for a compliant cookie consent mechanism. Furthermore, the has_privacy_policy data point is false, which is another significant compliance gap. A clear and accessible privacy policy is a legal requirement in many jurisdictions and essential for user trust, detailing how user data is collected, processed, and stored.

    Image Optimization & Performance

    a.lup.dev demonstrates a strong commitment to image optimization, which positively impacts performance. The site leverages Jetpack Photon (WordPress) as an image CDN, which efficiently serves and optimizes images. Crucially, lazy loading (has_lazy_loading: true) is enabled, ensuring images only load when they enter the viewport, significantly reducing initial page load times. The site also supports modern image formats, specifically WebP (has_webp: true), which provides superior compression without sacrificing quality, further enhancing performance. Additionally, responsive images (has_responsive_images: true) are implemented, serving appropriately sized images based on the user's device and screen resolution. The absence of AVIF (has_avif: false) support indicates a minor opportunity for further optimization, as AVIF can offer even better compression than WebP. No ad networks were detected on the site.

    Professional Verdict

    a.lup.dev presents a technically sound foundation, built on WordPress with Nginx and Hetzner hosting, showcasing a preference for performance and developer-friendly tools like Tailwind CSS. Its image optimization strategy is exemplary, contributing to a respectable load time. However, the site's technical maturity is hampered by critical omissions in SEO meta tags, a missing robots.txt, and a complete absence of email security protocols. Furthermore, the lack of a cookie consent mechanism and privacy policy poses significant compliance risks. Addressing these gaps is paramount for enhancing discoverability, trust, security, and legal adherence, moving a.lup.dev towards a truly robust and compliant digital presence.

    Analysis by StackOptic AIApr 14, 2026

    AI-Powered Insights

    Historical Analysis & Change Tracking