Website review, no card needed

sis.bg logo

sis.bg website review

Visit site (opens in a new tab)Reviewed 7 November 202632 issues · 75 checks

This review found 32 issues worth fixing on sis.bg, 17 of them high impact, across 75 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of sis.bg (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sis.bg at 0.7 s0.7 s
  2. sis.bg at 1.4 s1.4 s
  3. sis.bg at 2.0 s2.0 s
  4. sis.bg at 2.7 s2.7 s
  5. sis.bg at 3.4 s3.4 s
  6. sis.bg at 4.1 s4.1 s
  7. sis.bg at 4.7 s4.7 s
  8. sis.bg at 5.4 s5.4 s

Speed

10 to fix50
  • Use efficient cache lifetimes

    13.9 s · 4.6 MB

    91 files are served with short cache lifetimes, so returning visitors download them again (4.6 MB).

  • Render-blocking requests

    14.1 s

    64 files block the first paint until they finish downloading. Deferring or inlining them could save about 14.1 s.

  • Reduce unused CSS

    8.1 s · 1.6 MB

    About 1.6 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 8.1 s faster on a phone.

  • Reduce unused JavaScript

    1.4 s · 832 KiB

    About 832 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Minify CSS

    1.6 s · 338 KiB

    338 KiB could be saved by minifying CSS.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.5 MB and 870 ms of main-thread time.

  • Mobile performance score: 50

    50/100

    Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.

  • Google CDN adds 419 ms

    419 ms

    Google CDN costs a phone 419 ms of main-thread work and 736 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.

  • Google Tag Manager adds 337 ms

    337 ms

    Google Tag Manager costs a phone 337 ms of main-thread work and 610 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.

  • Main-thread work: 2.8 s

    A phone's processor spends 2.8 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 12 long tasks on the main thread

    12 long tasks block the main thread while loading, the longest for 206 ms. During a long task the page ignores taps.

  • Document request latency

    105 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Legacy JavaScript

    26 KiB

    Polyfills for old browsers add 26 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    12 KiB

    12 KiB could be saved by minifying JavaScript.

  • 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.

1 checks passed
  • Server response: 263 ms

    263 ms

    Your server sent the HTML in 263 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix61
  • First Contentful Paint: 12.8 s

    12.8 s

    The first text or image appears after 12.8 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 17.3 s

    17.3 s

    Your largest element takes 17.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ИНВЕСТИЦИОНЕН ПОСРЕДНИК SIS.С ГРИЖА ЗА ВАШИТЕ ФИНАНСИ ЗА НАС”.

  • Time to Interactive: 27.2 s

    27.2 s

    The page becomes fully interactive after 27.2 s. Good is under 3.8 s.

  • Speed Index: 12.8 s

    12.8 s

    Visually, the page fills in at 12.8 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 266 ms

    266 ms

    Scripts block taps and scrolling for 266 ms in total while the page loads. Good is under 200 ms.

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0.002

    0.002

    The layout barely moves while loading (CLS 0.002, good is under 0.1).

Images and page weight

3 to fix45
  • Page weight: 6.6 MB in 120 requests

    6.6 MB

    Your homepage downloads 6.6 MB in 120 requests on a phone: images 2.3 MB (16), scripts 1.9 MB (48) and stylesheets 1.7 MB (40). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    logo-1024x831-1.jpg weighs 1.8 MB. On a phone connection a single image that size takes seconds.

  • 6 images in older formats

    6 images (2.2 MB) are 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 1.9 g of CO₂ per visit

    1.87 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.87 g of CO₂e: 224.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 7893
  • 104 text elements with low contrast

    104 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h4 → h6), which makes the page harder to scan with a screen reader.

1 checks passed
  • 43 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: 43 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9288
  • Title is short (29 characters)

    Your title is only 29 characters: “Инвестиционен посредник - SIS”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Инвестиционен посредник SIS. С грижа за Вашите фи…” and “Инвестиционен посредник SIS.С грижа за Вашите фин…”). One clear main headline is easier for people and search engines.

  • 87 internal links, 5 external

    The homepage links to 87 pages on sis.bg and 5 external pages.

6 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “SIS e водещ инвестиционен посредник, предлагащ управление на активи, брокерски услуги и инвестиционни консултации в обл…”.

  • Canonical URL set

    The canonical URL is https://sis.bg/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://sis.bg/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://sis.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.

3 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (416 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 10 pages without a meta description

    https://sis.bg/za-nas/nashata-misiya, https://sis.bg/za-nas/ekip, https://sis.bg/deinosti, https://sis.bg/deinosti/brokerski-uslugi, https://sis.bg/deinosti/doveritelno-upravlenie and https://sis.bg/deinosti/finansovi-analizi and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages with very little text

    https://sis.bg/za-nas/nashata-misiya, https://sis.bg/za-nas/ekip, https://sis.bg/deinosti, https://sis.bg/deinosti/brokerski-uslugi, https://sis.bg/deinosti/doveritelno-upravlenie and https://sis.bg/deinosti/finansovi-analizi and 4 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 8 pages slow to respond

    https://sis.bg/deinosti/doveritelno-upravlenie, https://sis.bg/deinosti/finansovi-analizi, https://sis.bg/deinosti/sis-bgtrader, https://sis.bg/category/aktsenti, https://sis.bg/category/aktsenti/novini and https://sis.bg/analizi and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 67 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    12 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://www.leadengine-wp.com/agency/wp-content/themes/leadengine/images/logo-2.png.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    11 of 12 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • 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.

  • About 399 words of copy

    The homepage carries about 399 words of visible text.

2 checks passed
  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks and 18 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 10 other companies contacted

    Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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 sis.bg, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
SuperHosting.BG Ltd.

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on sis.bg, including 16 speed issues, 2 SEO issues and 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25