Website review, no card needed

rufostudio.com logo

rufostudio.com website review

Visit site (opens in a new tab)Reviewed 8 November 202622 issues · 75 checks

This review found 22 issues worth fixing on rufostudio.com, 6 of them high impact, across 75 checks. The most urgent: render-blocking 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

Full-page screenshot of rufostudio.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rufostudio.com at 0.8 s0.8 s
  2. rufostudio.com at 1.7 s1.7 s
  3. rufostudio.com at 2.5 s2.5 s
  4. rufostudio.com at 3.4 s3.4 s
  5. rufostudio.com at 4.2 s4.2 s
  6. rufostudio.com at 5.0 s5.0 s
  7. rufostudio.com at 5.9 s5.9 s
  8. rufostudio.com at 6.7 s6.7 s

Speed

5 to fix71
  • Render-blocking requests

    3.4 s

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

  • Font display

    1.6 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.6 s).

  • Mobile performance score: 71

    71/100

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

  • Reduce unused JavaScript

    600 ms · 119 KiB

    About 119 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 39 KiB

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

  • Improve image delivery

    115 KiB

    5 images could be 115 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 157 KiB and 87 ms of main-thread time.

  • 1 long task on the main thread

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

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

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

  • Server response: 235 ms

    235 ms

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

Core Web Vitals

4 to fix72
  • Speed Index: 8.1 s

    8.1 s

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

  • Largest Contentful Paint: 5.2 s

    5.2 s

    Your largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Transforming Ideas into Digital Products”. Most of its time is element render delay (3.6 s).

  • Time to Interactive: 5.2 s

    5.2 s

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

  • 10 images without width and height

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

3 checks passed
  • Cumulative Layout Shift: 0.088

    0.088

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

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

  • Total Blocking Time: 10 ms

    10 ms

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

Images and page weight

100
  • 5 images below the first screen load straight away

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

  • About 0.3 g of CO₂ per visit

    0.30 g

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

3 checks passed
  • Page weight: 1.0 MB in 88 requests

    1.0 MB

    Your homepage downloads 1.0 MB in 88 requests on a phone: scripts 382 KiB (28), images 366 KiB (20) and fonts 210 KiB (5). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

6 to fixGoogle 8290
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 3 text elements with low contrast

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 4 links without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 33 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 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

Google 100100
  • 23 internal links, 18 external

    The homepage links to 23 pages on rufostudio.com and 18 external pages.

8 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “RufoStudio is crafting Digital Experiences for SaaS, B2B, and B2C. We design Amazing Websites, Web, and Mobile Apps for…”.

  • One H1 headline

    Your main headline reads: “Transforming Ideas into Digital Products”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “RufoStudio - UX Design Studio and Agency based in Dhaka”.

  • Canonical URL set

    The canonical URL is https://rufostudio.com/.

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and ProfessionalService.

  • 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://rufostudio.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

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 contact details; sameAs (social profiles) and description would complete it.

  • Text is in the HTML

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

Other pages

5 to fix76
  • 2 pages share a title

    https://rufostudio.com/contact and https://rufostudio.com/corporate/contact all use the title “Connect with RufoStudio - A Creative UI/UX Design Agency - RufoStudio”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://rufostudio.com/blog and https://rufostudio.com/category/ux-case-study have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://rufostudio.com/work and https://rufostudio.com/products use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://rufostudio.com/corporate/contact, whose canonical is https://rufostudio.com/contact. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://rufostudio.com/work and https://rufostudio.com/products have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://rufostudio.com/products, https://rufostudio.com/blog, https://rufostudio.com/contact, https://rufostudio.com/corporate/contact and https://rufostudio.com/category/ux-case-study 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.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 12 pages we checked loaded without an error.

  • 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

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “elementorFrontend.waypoint is not a function”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 296 words of copy

    The homepage carries about 296 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get in Touch” and “Contact”.

  • 19 calls to action

    The homepage has 19 calls to action, for example “Contact”, “Get in Touch” and “Learn More”.

  • Social proof on the page

    Social proof on the homepage: 38 testimonial or review blocks, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 2 cookies set on arrival

    2

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

  • 2 other companies contacted

    Loading the homepage contacts 2 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 rufostudio.com, 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
Hosting
Hostinger

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on rufostudio.com, including 9 speed issues. 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