Website review, no card needed

mallofmontenegro.com logo

mallofmontenegro.com website review

Visit site (opens in a new tab)Reviewed 11 November 202648 issues · 83 checks

This review found 48 issues worth fixing on mallofmontenegro.com, 18 of them high impact, across 83 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 mallofmontenegro.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mallofmontenegro.com at 0.9 s0.9 s
  2. mallofmontenegro.com at 1.8 s1.8 s
  3. mallofmontenegro.com at 2.7 s2.7 s
  4. mallofmontenegro.com at 3.6 s3.6 s
  5. mallofmontenegro.com at 4.5 s4.5 s
  6. mallofmontenegro.com at 5.4 s5.4 s
  7. mallofmontenegro.com at 6.3 s6.3 s
  8. mallofmontenegro.com at 7.1 s7.1 s

Speed

6 to fix31
  • Use efficient cache lifetimes

    5.8 s · 7.5 MB

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

  • Render-blocking requests

    6.6 s

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

  • Reduce unused JavaScript

    2.4 s · 425 KiB

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

  • Mobile performance score: 31

    31/100

    Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Improve image delivery

    550 ms · 1.6 MB

    29 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.

  • Legacy JavaScript

    450 ms · 38 KiB

    Polyfills for old browsers add 38 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

  • Minify JavaScript

    160 ms · 41 KiB

    41 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    160 ms · 35 KiB

    About 35 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 160 ms faster on a phone.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 52 ms. During a long task the page ignores taps.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google/Doubleclick Ads and Google Fonts), adding 55 KiB and 41 ms of main-thread time.

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 231 ms of it running JavaScript. That is comfortably low.

  • Server response: 192 ms

    192 ms

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

Core Web Vitals

6 to fix34
  • Largest Contentful Paint: 12.6 s

    12.6 s

    Your largest element takes 12.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “bonatti 23septebmar”.

  • Cumulative Layout Shift: 0.995

    0.995

    The layout shifts by 0.995 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 6.7 s

    6.7 s

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

  • Speed Index: 13.4 s

    13.4 s

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

  • Time to Interactive: 12.9 s

    12.9 s

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

  • 140 images without width and height

    140 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
  • Total Blocking Time: 1 ms

    1 ms

    Scripts block the page for only 1 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix18
  • Page weight: 7.5 MB in 143 requests

    7.5 MB

    Your homepage downloads 7.5 MB in 143 requests on a phone: images 6.6 MB (89), scripts 861 KiB (34) and stylesheets 90 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1.2 MB together. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    1.1 MB

    6 images are downloaded at several times the size a phone draws them, for example George and friends logo.jpg at 2,693 px wide, shown at 104 px. Resized copies would save about 1.1 MB.

  • 29 images in older formats

    29 images (5.4 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.

  • 27 images below the first screen load straight away

    27 images further down the page (5.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.1 g of CO₂ per visit

    2.13 g

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

Accessibility

9 to fixGoogle 6085
  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (15 elements)

    All page content should be contained by landmarks: 15 elements on the page fail 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

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

  • <td> elements in a large <table> do not have table headers.

    <td> elements in a large <table> do not have table headers. (1 element).

1 checks passed
  • 27 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 27 passed and 8 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

10 to fixGoogle 8257
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (18 characters)

    Your title is only 18 characters: “Mall of Montenegro”. 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.

  • Meta description is short (52 characters)

    Your meta description is only 52 characters: “Šoping centar Mall of Montenegro Podgorica Crna Gora”. 70 to 160 characters is enough to sell the click.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at http://www.mallofmontenegro.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at mallofmontenegro.com/robots.txt, the first file search crawlers ask for.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 70 internal links, 5 external

    The homepage links to 70 pages on mallofmontenegro.com and 5 external pages.

AI search readiness

1 to fix88
  • 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://www.mallofmontenegro.com/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.

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

3 to fix86
  • 4 pages share a title

    https://www.mallofmontenegro.com/mall/index.php/bs-BA, https://www.mallofmontenegro.com/mall/index.php/en, https://www.mallofmontenegro.com/mall/index.php/bs-BA/component/content/article/10-aktuelnosti/1071-sajam-zdrave-hrane-2026-novembar and https://www.mallofmontenegro.com/mall/index.php/bs-BA/component/content/article/10-aktuelnosti/1070-nova-jesenja-kolekcija all use the title “Mall of Montenegro”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages share a meta description

    https://www.mallofmontenegro.com/mall/index.php/bs-BA/aktuelnos, https://www.mallofmontenegro.com/mall/index.php/bs-BA/zakupci/shopping, https://www.mallofmontenegro.com/mall/index.php/bs-BA/zakupci/zabava, https://www.mallofmontenegro.com/mall/index.php/bs-BA/zakupci/hrana-i-pice, https://www.mallofmontenegro.com/mall/index.php/bs-BA/zakupci/usluge and https://www.mallofmontenegro.com/mall/index.php/bs-BA/zakupci/zdravlje-i-ljepota and 8 others use the same meta description. A description written for each page earns more clicks.

  • 13 pages without an H1

    https://www.mallofmontenegro.com/mall/index.php/bs-BA/aktuelnos, https://www.mallofmontenegro.com/mall/index.php/bs-BA/zakupci/shopping, https://www.mallofmontenegro.com/mall/index.php/bs-BA/zakupci/zabava, https://www.mallofmontenegro.com/mall/index.php/bs-BA/zakupci/hrana-i-pice, https://www.mallofmontenegro.com/mall/index.php/bs-BA/zakupci/usluge and https://www.mallofmontenegro.com/mall/index.php/bs-BA/zakupci/zdravlje-i-ljepota and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.mallofmontenegro.com/mall/index.php/bs-BA/galerija and https://www.mallofmontenegro.com/mall/index.php/en 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.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 5270
  • 1 broken image

    1 image failed to load on a phone, for example https://www.mallofmontenegro.com/mall/images/sampledata/slideglavni/mall05.jpg.

  • 8 small tap targets

    8 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://www.mallofmontenegro.com/mall/index.php/bs-BA' was loaded over HTTPS, but requested…”.

  • 4 low-resolution images

    4 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 197 words

    The homepage has only about 197 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “[object Object]”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Privacy and tracking

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 1 other company contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

  • The footer still says © 2013.

Stack

CMS
Joomla
Framework
jQuery
Hosting
One Crna Gora DOO

Company

Founded
2009

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 mallofmontenegro.com, including 12 speed issues, 10 SEO issues and 4 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