Website review, no card needed

imgsrc.ru logo

imgsrc.ru website review

Visit site (opens in a new tab)Reviewed 11 October 202626 issues · 72 checks

This review found 26 issues worth fixing on imgsrc.ru, 9 of them high impact, across 72 checks. The most urgent: page weight: 14.1 MB in 66 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
729 ms617 msApr 18Oct 3716 ms
Show as table
DateReal-visitor load time (LCP)
Apr 18, 2026630 ms
Apr 25, 2026638 ms
May 2, 2026645 ms
May 9, 2026645 ms
May 16, 2026644 ms
May 23, 2026647 ms
May 30, 2026651 ms
Jun 6, 2026663 ms
Jun 13, 2026674 ms
Jun 20, 2026688 ms
Jun 27, 2026700 ms
Jul 4, 2026707 ms
Jul 11, 2026711 ms
Jul 18, 2026710 ms
Jul 25, 2026706 ms
Aug 1, 2026700 ms
Aug 8, 2026699 ms
Aug 15, 2026700 ms
Aug 22, 2026700 ms
Aug 29, 2026698 ms
Sep 5, 2026694 ms
Sep 12, 2026690 ms
Sep 19, 2026694 ms
Sep 26, 2026709 ms
Oct 3, 2026716 ms
Real-visitor tap response (INP)75th percentile, phones
83 ms76 msApr 18Oct 377 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 202682 ms
Apr 25, 202682 ms
May 2, 202681 ms
May 9, 202681 ms
May 16, 202681 ms
May 23, 202681 ms
May 30, 202681 ms
Jun 6, 202681 ms
Jun 13, 202681 ms
Jun 20, 202682 ms
Jun 27, 202682 ms
Jul 4, 202682 ms
Jul 11, 202682 ms
Jul 18, 202682 ms
Jul 25, 202682 ms
Aug 1, 202682 ms
Aug 8, 202682 ms
Aug 15, 202682 ms
Aug 22, 202681 ms
Aug 29, 202680 ms
Sep 5, 202679 ms
Sep 12, 202678 ms
Sep 19, 202678 ms
Sep 26, 202677 ms
Oct 3, 202677 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 imgsrc.ru (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. imgsrc.ru at 0.4 s0.4 s
  2. imgsrc.ru at 0.8 s0.8 s
  3. imgsrc.ru at 1.1 s1.1 s
  4. imgsrc.ru at 1.5 s1.5 s
  5. imgsrc.ru at 1.9 s1.9 s
  6. imgsrc.ru at 2.3 s2.3 s
  7. imgsrc.ru at 2.6 s2.6 s
  8. imgsrc.ru at 3.0 s3.0 s

Speed

7 to fix74
  • Render-blocking requests

    1.1 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.1 s.

  • Use efficient cache lifetimes

    10.5 MB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Fonts and icdn.ru), adding 14.1 MB and 0 ms of main-thread time.

  • icdn.ru adds 0 ms

    0 ms

    icdn.ru costs a phone 0 ms of main-thread work and 10.5 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.

  • Mobile performance score: 74

    74/100

    Your mobile performance score is 74 (desktop: 76). Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    381 KiB

    1 image could be 381 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Google Fonts adds 0 ms

    0 ms

    Google Fonts costs a phone 0 ms of main-thread work and 3.6 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.

  • 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: 0.3 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

5 to fix67
  • 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.

  • Largest Contentful Paint: 21.6 s

    21.6 s

    Your largest element takes 21.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “photo Miasto pierników i Kopernika © verkeus”.

  • Time to Interactive: 21.8 s

    21.8 s

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

  • Real-user INP: 311 ms

    311 ms

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

  • Real-user TTFB: 969 ms

    969 ms

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

  • Tap response (INP) held steady for real visitors

    -6%

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

  • Largest content (LCP) got 12% slower for real visitors

    +12%

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

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

  • First Contentful Paint: 1.5 s

    1.5 s

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

  • Speed Index: 2.4 s

    2.4 s

    Visually, the page fills in at 2.4 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.031

    0.031

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

  • 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

3 to fix35
  • Page weight: 14.1 MB in 66 requests

    14.1 MB

    Your homepage downloads 14.1 MB in 66 requests on a phone: images 10.5 MB (61), fonts 3.6 MB (3) and HTML 7 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 30 images far larger than shown

    5.2 MB

    30 images are downloaded at several times the size a phone draws them, for example 86382137fGK.webp at 3,185 px wide, shown at 65 px. Resized copies would save about 5.2 MB.

  • 1 image over 500 KB

    86382137fGK.webp weighs 969 KiB. On a phone connection a single image that size takes seconds.

  • About 4.0 g of CO₂ per visit

    4.00 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

Accessibility

3 to fixGoogle 9092
  • Links look like plain text

    4 links inside paragraphs rely on colour alone to stand out.

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

    All page content should be contained by landmarks: 5 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.

2 checks passed
  • Every image has alt text

    All 61 images in the HTML carry an alt attribute.

  • 20 automated accessibility rules passed

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

SEO

3 to fixGoogle 10089
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 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 https://imgsrc.ru/cameras/sitemap.txt, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

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

  • 82 internal links, 1 external

    The homepage links to 82 pages on imgsrc.ru and 1 external page.

5 checks passed
  • Meta description: 71 characters

    Your meta description is 71 characters: “Your free and unlimited host iMGSRC.RU presents Unlimited photo hosting”.

  • One H1 headline

    Your main headline reads: “Unlimited photo hosting”.

  • Title: 34 characters

    Your title is a healthy 34 characters: “Unlimited photo hosting @iMGSRC.RU”.

  • Canonical URL set

    The canonical URL is https://imgsrc.ru/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

1 to fix83
  • 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.

  • Opted out of AI training for 1 crawler

    robots.txt blocks GPTBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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.

Other pages

100
  • 10 pages with very little text

    https://imgsrc.ru/verkeus/86495337.html, https://imgsrc.ru/sweetlana/86668889.html, https://imgsrc.ru/9174337478/86590534.html, https://imgsrc.ru/9174337478/85867942.html, https://imgsrc.ru/jazz-sax/86382137.html and https://imgsrc.ru/9174337478/86476072.html 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.

  • 4 pages slow to respond

    https://imgsrc.ru/verkeus/86495337.html, https://imgsrc.ru/verkeus, https://imgsrc.ru/sweetlana/86668889.html and https://imgsrc.ru/9174337478/86590534.html took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 11 pages that loaded have a meta description.

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

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    60 of 70 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix58
  • 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.

  • Only about 137 words

    The homepage has only about 137 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.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Join now”.

  • 1 call to action

    The homepage has 1 call to action, for example “Join now”.

Privacy and tracking

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

  • 9 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on imgsrc.ru, including 12 speed issues, 3 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