workwise.io

We performed a comprehensive analysis of workwise.io on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 7451ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 706 KB, and the site is served behind a CDN (Content Delivery Network). The website uses a secure HTTPS connection with a valid SSL certificate issued by Google Trust Services (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and ECDSA-SHA256 signature algorithm. The certificate covers 4 domain(s) (Subject Alternative Names) and expires on 2026-09-18, which is 80 days from now. The security headers analysis reveals a score of 0/100 (poor). No security headers are configured, which is a significant security concern. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy, which could expose the site and its users to cross-site scripting (XSS), clickjacking, and other web-based attacks. Our technology detection scan identified 8 technologies across 6 categories powering workwise.io. The detected stack includes Next.js images, Angular, React, Webpack, Vite, Amazon CloudFront, Adobe Fonts, and jQuery 3.5.1.. The site uses Next.js as its primary framework (version images). The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, workwise.io receives an overall trust score of 68/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, workwise.io receives a trust score of 68/100, which places it in the "Likely Safe" category. This score is calculated by evaluating multiple factors including SSL certificate validity, domain registration history, email authentication protocols, security header configuration, and blacklist status across major threat intelligence databases. The analysis identified several positive trust signals: a valid HTTPS connection protecting data in transit, a valid SSL certificate issued by Google Trust Services with 80 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a reject policy — the strongest available setting. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking), missing Referrer-Policy, potentially leaking URL information to third parties, the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity, and DNSSEC is not enabled, leaving DNS queries vulnerable to spoofing attacks. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked workwise.io against 8 major blacklist databases including Google Safe Browsing, Phishtank, Urlhaus, Openphish, Dnsfilter, Spamhaus Dbl, Surbl, and Virustotal. The domain passed all 8 checks with a clean status, meaning it has not been flagged for phishing, malware distribution, spam, or other malicious activities by any of the tested threat intelligence providers.

Our technology detection engine scanned workwise.io and identified 8 distinct technologies across 6 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Framework: Next.js (version images) and Angular — provides the application framework and routing for workwise.io. UI Library: React — handles the user interface rendering and component management for workwise.io. Build Tool: Webpack and Vite — bundles and optimizes the JavaScript and CSS assets for workwise.io. CDN: Amazon CloudFront — accelerates content delivery by caching assets at edge locations worldwide for workwise.io. Fonts: Adobe Fonts — delivers web fonts for typography for workwise.io. JavaScript Library: jQuery (version 3.5.1.) — provides utility functions and DOM manipulation for workwise.io.

workwise.io delivers its homepage in 7451ms (server response time), which is considered slow by industry standards. The total page weight is 706 KB, and we detected 237 resource requests loading assets from 9 third-party domains. A high number of third-party domains can significantly impact page load time due to additional DNS lookups and TLS handshakes required for each domain. The website uses Gzip compression for text-based assets, achieving an estimated 60.0% reduction in transfer size. This reduces bandwidth usage and improves page load times, especially for visitors on slower connections. Asset minification status: 2 out of 3 CSS files and 3 out of 15 JavaScript files are minified. Minifying the remaining 13 unminified file(s) could further reduce page weight by 10-30% for those assets. Minification is a best practice that reduces download sizes without affecting functionality. The site is served through a Content Delivery Network (CDN), which caches static assets at edge servers around the world. This means visitors from different geographic regions receive content from the nearest edge server, significantly reducing latency. CDN usage is particularly important for websites with a global audience, as it can reduce page load times by 40-60% for distant visitors. From an environmental perspective, each page view of workwise.io produces approximately 0.34g of CO₂, earning a carbon rating of C. This is an average carbon footprint. Optimizing images and reducing unnecessary scripts could further improve this score. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 706 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for workwise.io. This typically means the site doesn't have enough real-world Chrome user traffic to generate statistically significant field data, or the domain is not included in the CrUX dataset. Core Web Vitals (LCP, INP, CLS) are important Google ranking factors that measure real user experience.

workwise.io resolves to the IPv4 address 172.67.74.82 and also supports IPv6 (2606:4700:20::681a:31b), demonstrating modern network infrastructure readiness. The domain has 3 A record(s) configured. The domain name system is managed by 2 name servers: lynn.ns.cloudflare.com and tani.ns.cloudflare.com. Having 2 name servers provides good redundancy — if one fails, the others can continue serving DNS queries. The choice of name servers often indicates the DNS hosting provider or CDN service being used. Email for workwise.io is handled by Google Workspace with 5 MX records configured: aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com and 2 more. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. SPF (Sender Policy Framework) is configured, which specifies which mail servers are authorized to send email on behalf of this domain. This helps prevent email spoofing and improves email deliverability. DMARC (Domain-based Message Authentication, Reporting and Conformance) is configured with a reject policy — the strongest setting, instructing receiving servers to reject unauthorized emails entirely. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is not enabled for workwise.io. While not critical for most websites, DNSSEC adds an important security layer by ensuring DNS responses haven't been tampered with during transit. Enabling DNSSEC is recommended for domains handling sensitive data or financial transactions.

The homepage of workwise.io contains 960 words of visible text content. This is a moderate amount of content. The page is structured with 18 H2 headings, 0 H3 headings, 1 H4 headings. The page includes 119 images. 21 images (18%) are missing alt text attributes, which is a significant concern for both accessibility and SEO. Screen readers rely on alt text to describe images to visually impaired users, and search engines use alt text to understand image content. Only 82% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 73 internal links pointing to other pages on the same domain and 13 external links pointing to third-party websites. There are 15 external JavaScript files, 3 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages), robots.txt (controls search engine crawling behavior), Schema.org structured data (Organization and PostalAddress), and Progressive Web App (PWA) manifest (enabling app-like installation). The website has social media presence across 4 platforms: Facebook (@WorkwiseSocial), Twitter (@WorkwiseSocial), Instagram (@workwiseofficial), and Linkedin (@workwise-gmbh). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for workwise.io is well-optimized at 50 characters: "Workwise – Jobs & Stellenangebote ohne Anschreiben". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 159 characters (acceptable): "Bewirb dich ohne Anschreiben auf deinen nächsten Job – mit garantierter Rückmeldung. Mit Workwise findest du passende Jo...". Google typically displays up to 155-160 characters of the meta description in search results. A compelling meta description with a clear call-to-action can significantly improve click-through rates from search results. The canonical url is correctly set to https://www.workwise.io/_desktop/_main, preventing duplicate content issues, the page language is declared as de, the meta robots directive is set to index,follow, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Workwise – Jobs & Stellenangebote ohne Anschreiben..."), OG description, OG image (social sharing thumbnail), OG type (website). These tags control how the page appears when shared on Facebook, LinkedIn, and other social media platforms that support the Open Graph protocol. A Twitter Card of type summary_large_image is configured, which controls how links appear when shared on Twitter/X. The "summary_large_image" type displays a large image preview, which typically generates higher engagement rates than the basic card type. The site implements Schema.org structured data with the following types: Organization and PostalAddress. Structured data helps search engines understand the page content and can enable rich results (featured snippets, knowledge panels, star ratings) in Google search results, which can significantly increase click-through rates.