yaga.co.za

We performed a comprehensive analysis of yaga.co.za on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 18415ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 1086 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 Amazon (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_128_GCM_SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-12-04, which is 157 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 7 technologies across 6 categories powering yaga.co.za. The detected stack includes Next.js css, Webpack, Vite, Google Analytics 4, Google Tag Manager, Sentry, and Google Fonts. The site uses Next.js as its primary framework (version css). Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, yaga.co.za receives an overall trust score of 66/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, yaga.co.za receives a trust score of 66/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 Amazon with 157 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a none policy. 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 yaga.co.za 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 yaga.co.za and identified 7 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 css) — provides the application framework and routing for yaga.co.za. Build Tool: Webpack and Vite — bundles and optimizes the JavaScript and CSS assets for yaga.co.za. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for yaga.co.za. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for yaga.co.za. Monitoring: Sentry — monitors application performance and errors for yaga.co.za. Fonts: Google Fonts — delivers web fonts for typography for yaga.co.za. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-N57BRMD2J4 and Google Tag Manager container GTM-M3GMVJX. These IDs can be used to identify other websites operated by the same organization.

yaga.co.za delivers its homepage in 18415ms (server response time), which is considered slow by industry standards. The total page weight is 1086 KB, and we detected 104 resource requests loading assets from 3 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: 0 out of 2 CSS files and 0 out of 11 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 yaga.co.za produces approximately 0.53g of CO₂, earning a carbon rating of D. The website's carbon footprint could be reduced by optimizing images, enabling compression, reducing third-party scripts, and leveraging caching. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 1086 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for yaga.co.za. 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.

yaga.co.za resolves to the IPv4 address 13.33.235.38, but does not support IPv6. IPv6 adoption is increasingly important as IPv4 address space becomes exhausted, and some ISPs and regions are transitioning to IPv6-only connectivity. The domain has 4 A record(s) configured. The domain name system is managed by 4 name servers: ns-1116.awsdns-11.org, ns-1882.awsdns-43.co.uk, ns-223.awsdns-27.com, and ns-588.awsdns-09.net. Having 4 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 yaga.co.za is handled by Google Workspace with 1 MX records configured: smtp.google.com. 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 none policy — a monitoring-only setting that doesn't enforce any action on unauthorized emails. 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 yaga.co.za. 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 yaga.co.za contains 97 words of visible text content. This is a relatively short page — adding more descriptive content could improve search engine visibility. The page is structured with 0 H2 headings, 6 H3 headings, 0 H4 headings. The page includes 50 images. 13 images (26%) 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 74% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 38 internal links pointing to other pages on the same domain and 0 external links pointing to third-party websites. There are 11 external JavaScript files, 2 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), and Schema.org structured data (BreadcrumbList and ListItem). We detected the following payment methods accepted on yaga.co.za: Visa, Mastercard, American Express, Discover, and JCB. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates. The website has social media presence across 2 platforms: Facebook (@shopyaga) and Instagram (@shopyaga). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for yaga.co.za is well-optimized at 39 characters: "Yaga - marketplace for preloved fashion". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 214 characters (slightly long): "Yaga is an online selling and shopping platform for new and preloved fashion. Buy preloved clothing safely or open your ...". 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.yaga.co.za, preventing duplicate content issues, the page language is declared as en, and the meta robots directive is set to index,follow. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Yaga - marketplace for preloved fashion..."), 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. The site implements Schema.org structured data with the following types: BreadcrumbList and ListItem. 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.