Website review, no card needed

niftycity.shop logo

niftycity.shop website review

Visit site (opens in a new tab)Reviewed 8 November 202631 issues · 79 checks

This review found 31 issues worth fixing on niftycity.shop, 8 of them high impact, across 79 checks. The most urgent: page weight: 17.7 MB in 402 requests. 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

Real-visitor load time (LCP)75th percentile, phones
2.3 s1.8 sMay 16Oct 311.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.3 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.1 s
Aug 29, 20262.0 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.8 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Oct 31, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
97 ms88 msMay 16Oct 3193 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202695 ms
May 23, 202695 ms
May 30, 202695 ms
Jun 6, 202695 ms
Jun 13, 202695 ms
Jun 20, 202696 ms
Jun 27, 202695 ms
Jul 4, 202695 ms
Jul 11, 202695 ms
Jul 18, 202693 ms
Jul 25, 202692 ms
Aug 1, 202693 ms
Aug 8, 202690 ms
Aug 15, 202691 ms
Aug 22, 202691 ms
Aug 29, 202690 ms
Sep 5, 202694 ms
Sep 12, 202695 ms
Sep 19, 202696 ms
Sep 26, 202695 ms
Oct 3, 202693 ms
Oct 10, 202692 ms
Oct 17, 202689 ms
Oct 24, 202691 ms
Oct 31, 202693 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

Full-page screenshot of niftycity.shop (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. niftycity.shop at 0.9 s0.9 s
  2. niftycity.shop at 1.8 s1.8 s
  3. niftycity.shop at 2.7 s2.7 s
  4. niftycity.shop at 3.6 s3.6 s
  5. niftycity.shop at 4.4 s4.4 s
  6. niftycity.shop at 5.3 s5.3 s
  7. niftycity.shop at 6.2 s6.2 s
  8. niftycity.shop at 7.1 s7.1 s

Speed

11 to fix70
  • Reduce unused JavaScript

    1.3 s · 493 KiB

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

  • 3,539 HTML elements

    The page has 3,539 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (OptiMonk, Shopify and loox.io and others), adding 6.4 MB and 560 ms of main-thread time.

  • Mobile performance score: 70

    70/100

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

  • Improve image delivery

    700 ms · 260 KiB

    10 images could be 260 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.

  • Render-blocking requests

    800 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

  • Shopify adds 96 ms

    96 ms

    Shopify costs a phone 96 ms of main-thread work and 5.3 MB 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.

  • Use efficient cache lifetimes

    300 ms · 275 KiB

    21 files are served with short cache lifetimes, so returning visitors download them again (275 KiB).

  • Main-thread work: 2.8 s

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

  • OptiMonk adds 144 ms

    144 ms

    OptiMonk costs a phone 144 ms of main-thread work and 314 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.

  • tidio.co adds 69 ms

    69 ms

    tidio.co costs a phone 69 ms of main-thread work and 515 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

    250 ms · 70 KiB

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

  • Reduce unused CSS

    150 ms · 57 KiB

    About 57 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.

  • 1 long task on the main thread

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

  • Duplicated JavaScript

    23 KiB

    23 KiB JavaScript is shipped twice across bundles.

  • Minify JavaScript

    21 KiB

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

  • 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: 7 ms

    7 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 11.9 s

    11.9 s

    Your largest element takes 11.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Three digital dashboard gauge displays shown in the vehicle…”.

  • Time to Interactive: 11.9 s

    11.9 s

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

  • Speed Index: 6.1 s

    6.1 s

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

  • Tap response (INP) held steady for real visitors

    -3%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 95 ms to 93 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -9%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 104 ms

    104 ms

    Real visitors wait 104 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.6 s

    1.6 s

    Real visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 552 ms

    552 ms

    Real visitors wait 552 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.001

    0.001

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

5 to fix43
  • Page weight: 17.7 MB in 402 requests

    17.7 MB

    Your homepage downloads 17.7 MB in 402 requests on a phone: media 13.0 MB (3), scripts 1.5 MB (122) and images 1.4 MB (31). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    1_a8361695-c3f9-481a-ba81-340e5a994bd8.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 9 images below the first screen load straight away

    9 images further down the page (974 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 6 images in older formats

    6 images (579 KiB) 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.

  • 4 images far larger than shown

    116 KiB

    4 images are downloaded at several times the size a phone draws them, for example 1_8525defd-374f-45f8-9c55-52addc28bf1a.jpg at 1,192 px wide, shown at 350 px. Resized copies would save about 116 KiB.

  • About 5.0 g of CO₂ per visit

    5.02 g

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

Accessibility

3 to fixGoogle 9296
  • 10 images without alt text

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

  • 2 links without text

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

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

2 to fixGoogle 9291
  • 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 long (298 characters)

    Your meta description is 298 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 406 internal links, 16 external

    The homepage links to 406 pages on niftycity.shop and 16 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Nifty City”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Nifty City - Apple CarPlay & Android Auto Integration”.

  • Canonical URL set

    The canonical URL is https://www.niftycity.shop/.

  • 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://www.niftycity.shop/sitemap.xml.

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.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.niftycity.shop/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 15 pages without a meta description

    https://www.niftycity.shop/collections/nissan-tesla-screens, https://www.niftycity.shop/collections/infiniti-tesla-screens, https://www.niftycity.shop/collections/gmc-tesla-screens, https://www.niftycity.shop/collections/chevrolet-tesla-screens, https://www.niftycity.shop/collections/ford-tesla-screens and https://www.niftycity.shop/collections/jeep-tesla-screens and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 4 JavaScript errors while loading

    4 errors were 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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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.

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

  • About 682 words of copy

    The homepage carries about 682 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP 370Z DIGITAL CLUSTER”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “Contact Us”, “Track Order” and “Product Request”.

  • 5 short forms

    5 short forms (3 fields at most) are right on the homepage, asking for an email.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 cookies, 1 of them by other companies (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.

  • 44 other companies contacted

    Loading the homepage contacts 44 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 niftycity.shop, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 20 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Partly Pim Smarter Auto Parts · Uppromote Affiliate · Warnify Pro Warnings · Optimonk Popup Cro A B Test · Candy Rack · Klaviyo Email Marketing Sms · Product Warnings · Announcement Bar Maker By Apphero · Affliate By Secomapp · Simple Bundle · loox.io · kxcdn.com · conversionbear.com · chaty.app · app-easy-product-downloads.fr · stock-counter.app · lay-buys.com · cloudfront.net · govedia.com · good-apps.co

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on niftycity.shop, including 14 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