lolis.jp

We performed a comprehensive analysis of lolis.jp on 2026-07-03. The website returned an HTTP 200 status code with a server response time of 34429ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 628 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by Let's Encrypt (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-09-11, which is 70 days from now. The security headers analysis reveals a score of 20/100 (poor). The following security headers are properly configured: Strict-Transport-Security (HSTS). However, the site is missing Content-Security-Policy, 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 6 technologies across 6 categories powering lolis.jp. The detected stack includes Next.js css, React, Webpack, Google Analytics 4, Google Tag Manager, and Amazon CloudFront. The site uses Next.js as its primary framework (version css). The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, lolis.jp receives an overall trust score of 64/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, lolis.jp receives a trust score of 64/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, HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks, and a valid SSL certificate issued by Let's Encrypt with 70 days until expiration. 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 lolis.jp 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 lolis.jp and identified 6 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 lolis.jp. UI Library: React — handles the user interface rendering and component management for lolis.jp. Build Tool: Webpack — bundles and optimizes the JavaScript and CSS assets for lolis.jp. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for lolis.jp. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for lolis.jp. CDN: Amazon CloudFront — accelerates content delivery by caching assets at edge locations worldwide for lolis.jp. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-6409MDLTTF and Google Tag Manager container GTM-T6MLXKL4. These IDs can be used to identify other websites operated by the same organization.

lolis.jp delivers its homepage in 34429ms (server response time), which is considered slow by industry standards. The total page weight is 628 KB, and we detected 502 resource requests loading assets from 18 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 3 CSS files and 0 out of 26 JavaScript files are minified. Minifying the remaining 29 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. From an environmental perspective, each page view of lolis.jp produces approximately 0.31g 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 628 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for lolis.jp. 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.

lolis.jp resolves to the IPv4 address 216.150.16.193, 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 2 A record(s) configured. The domain name system is managed by 2 name servers: ns1.vercel-dns.com and ns2.vercel-dns.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. SPF is not configured, meaning any server could potentially send emails pretending to be from this domain. This is a significant email security concern. DMARC is not configured, leaving the domain vulnerable to email spoofing and phishing attacks that impersonate this domain. 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 lolis.jp. 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 lolis.jp contains 1,083 words of visible text content. This is a substantial amount of content that provides good opportunities for search engine indexing. The page is structured with 22 H2 headings, 104 H3 headings, 0 H4 headings. The page includes 131 images. All images have proper alt text attributes ✓, which is excellent for both accessibility (screen readers) and SEO (search engines can understand image content). The link structure consists of 313 internal links pointing to other pages on the same domain and 13 external links pointing to third-party websites. The high number of internal links suggests a well-interconnected site structure, which helps search engines discover and crawl all pages efficiently. There are 26 external JavaScript files, 3 CSS stylesheets, and 2 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 (Answer, FAQPage, ImageObject, Organization, Question, and WebSite).

The title tag for lolis.jp is good at 70 characters: "ロリータファッション専門通販サイトLITALITA | ロリータファッション専門店ならではの品揃えでロリータファッションを取り揃えています！". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 117 characters (well-optimized): "ロリータファッションを探すならロリータファッション専門通販サイトLITALITA！ロリータファッション専門店ならではの品揃えでこだわりを持ってロリータファッションを探したい方にとって様々なロリータファッションを探せる最適なサイトです。". 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.lolis.jp, preventing duplicate content issues, the page language is declared as ja, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("ロリータファッション専門通販サイトLITALITA | ロリータファッション専門店ならではの品揃えでロリータファッション..."), 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: Answer, FAQPage, ImageObject, Organization, Question, and WebSite. 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.