Website review, no card needed
7arts.bg website review
Visit site (opens in a new tab)Reviewed 4 November 202648 issues · 73 checks
This review found 48 issues worth fixing on 7arts.bg, 26 of them high impact, across 73 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
50FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.4 s |
| May 23, 2026 | 4.4 s |
| May 30, 2026 | 4.4 s |
| Jun 6, 2026 | 4.5 s |
| Jun 13, 2026 | 4.6 s |
| Jun 20, 2026 | 4.7 s |
| Jun 27, 2026 | 4.7 s |
| Jul 4, 2026 | 4.8 s |
| Jul 11, 2026 | 4.8 s |
| Jul 18, 2026 | 4.8 s |
| Jul 25, 2026 | 4.9 s |
| Aug 1, 2026 | 4.9 s |
| Aug 8, 2026 | 4.9 s |
| Aug 15, 2026 | 4.9 s |
| Aug 22, 2026 | 4.9 s |
| Aug 29, 2026 | 4.8 s |
| Sep 5, 2026 | 4.9 s |
| Sep 12, 2026 | 4.9 s |
| Sep 19, 2026 | 5.1 s |
| Sep 26, 2026 | 5.4 s |
| Oct 3, 2026 | 5.4 s |
| Oct 10, 2026 | 5.2 s |
| Oct 17, 2026 | 5.2 s |
| Oct 24, 2026 | 5.3 s |
| Oct 31, 2026 | 5.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 189 ms |
| May 23, 2026 | 189 ms |
| May 30, 2026 | 187 ms |
| Jun 6, 2026 | 191 ms |
| Jun 13, 2026 | 195 ms |
| Jun 20, 2026 | 199 ms |
| Jun 27, 2026 | 206 ms |
| Jul 4, 2026 | 210 ms |
| Jul 11, 2026 | 222 ms |
| Jul 18, 2026 | 217 ms |
| Jul 25, 2026 | 223 ms |
| Aug 1, 2026 | 227 ms |
| Aug 8, 2026 | 227 ms |
| Aug 15, 2026 | 260 ms |
| Aug 22, 2026 | 286 ms |
| Aug 29, 2026 | 299 ms |
| Sep 5, 2026 | 305 ms |
| Sep 12, 2026 | 301 ms |
| Sep 19, 2026 | 298 ms |
| Sep 26, 2026 | 305 ms |
| Oct 3, 2026 | 313 ms |
| Oct 10, 2026 | 313 ms |
| Oct 17, 2026 | 322 ms |
| Oct 24, 2026 | 331 ms |
| Oct 31, 2026 | 331 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Use efficient cache lifetimes
12.3 s · 19.3 MB286 files are served with short cache lifetimes, so returning visitors download them again (19.3 MB).
Improve image delivery
9.8 s · 11.9 MB80 images could be 11.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.8 s faster on a phone.
Reduce unused JavaScript
4.9 s · 979 KiBAbout 979 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.9 s faster on a phone.
10,480 HTML elements
The page has 10,480 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 11
11/100Your mobile performance score is 11. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.5 s
A phone's processor spends 9.5 s on main-thread work while loading, 3.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Facebook, Google Tag Manager and Cookiebot and others), adding 581 KiB and 520 ms of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 560 ms. During a long task the page ignores taps.
Facebook adds 305 ms
305 msFacebook costs a phone 305 ms of main-thread work and 282 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Legacy JavaScript
150 ms · 56 KiBPolyfills for old browsers add 56 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 33 KiBAbout 33 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 7.1 s
7.1 sReal visitors wait 7.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 1.50
1.50For real visitors the layout shifts by 1.50 (75th percentile). Good is under 0.1.
Real-user FCP: 4.2 s
4.2 sReal visitors see the first content after 4.2 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 67.1 s
67.1 sYour largest element takes 67.1 s to render on a phone. Google's threshold for “good” is 2.5 s.
Time to Interactive: 70.5 s
70.5 sThe page becomes fully interactive after 70.5 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.906
0.906The layout shifts by 0.906 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 2.8 s
2.8 sScripts block taps and scrolling for 2.8 s in total while the page loads. Good is under 200 ms.
Speed Index: 8.4 s
8.4 sVisually, the page fills in at 8.4 s (Speed Index). Good is under 3.4 s.
Real-user INP: 440 ms
440 msReal visitors wait 440 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 75% slower for real visitors
+75%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 189 ms to 331 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.4 s to 5.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
1 checks passed
Real-user TTFB: 669 ms
669 msReal visitors wait 669 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 24.2 MB in 425 requests
24.2 MBYour homepage downloads 24.2 MB in 425 requests on a phone: images 20.5 MB (308), scripts 2.1 MB (22) and other files 1.5 MB (88). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 4.8 MB together. On a phone connection a single image that size takes seconds.
5 images far larger than shown
2.9 MB5 images are downloaded at several times the size a phone draws them, for example landscape.webp at 1,681 px wide, shown at 313 px. Resized copies would save about 2.9 MB.
32 images below the first screen load straight away
32 images further down the page (3.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (300 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 6.9 g of CO₂ per visit
6.87 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.87 g of CO₂e: 824.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (57 elements)
All page content should be contained by landmarks: 57 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (218 elements).
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (5 characters)
Your title is only 5 characters: “7arts”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No XML sitemap
No XML sitemap at https://7arts.bg/sitemap.xml, so Google discovers your pages only by following links.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
2 checks passed
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://7arts.bg/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
1 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Best practices
2 broken images
2 images failed to load on a phone, for example https://img.jwplayer.com/v1/media/6BZeel89/images/vertical.webp?poster_fallback=1&width=320.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'addEventListener')”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
82 of 90 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 52 words
The homepage has only about 52 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and Cloudflare Web Analytics.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
18 other companies contacted
Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at 7arts.bg, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on 7arts.bg, including 22 speed issues, 7 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.