Website review, no card needed

movexpk.com logo

movexpk.com website review

Visit site (opens in a new tab)Reviewed 18 October 202631 issues · 89 checks

This review found 31 issues worth fixing on movexpk.com, 13 of them high impact, across 89 checks. The most urgent: improve image delivery. 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

Live view · interaction off

Speed

6 to fix51
  • Improve image delivery

    5.3 s · 1,019 KiB

    5 images could be 1,019 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.3 s faster on a phone.

  • Use efficient cache lifetimes

    3.5 s · 670 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 51

    51/100

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Cloudflare, Google Fonts and pravatar.cc and others), adding 1.2 MB and 19 ms of main-thread time.

  • ligasumut.com adds 0 ms

    0 ms

    ligasumut.com costs a phone 0 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.

  • Legacy JavaScript

    21 KiB

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

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.3 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

5 to fix41
  • Largest Contentful Paint: 8.2 s

    8.2 s

    Your largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Popup Banner”.

  • Cumulative Layout Shift: 0.443

    0.443

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

  • Time to Interactive: 8.2 s

    8.2 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • 4 images without width and height

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

2 checks passed
  • Speed Index: 2.7 s

    2.7 s

    Visually, the page fills in at 2.7 s (Speed Index), inside the 3.4 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

3 to fix55
  • 1 image over 500 KB

    LOGO-SULE76.png weighs 728 KiB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    826 KiB

    2 images are downloaded at several times the size a phone draws them, for example LOGO-SULE76.png at 1,584 px wide, shown at 170 px. Resized copies would save about 826 KiB.

  • 3 images in older formats

    3 images (1.1 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 0.3 g of CO₂ per visit

    0.35 g

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

2 checks passed
  • Page weight: 1.2 MB in 20 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 20 requests on a phone: images 1.1 MB (10), fonts 74 KiB (4) and scripts 31 KiB (3). That is a lean page.

  • Images load when needed

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

Accessibility

5 to fixGoogle 8192
  • Unlabelled dropdowns

    2 dropdowns have no label.

  • 12 text elements with low contrast

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

  • Zoom is disabled

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

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

3 to fixGoogle 9283
  • Title is long (80 characters)

    Your title is 80 characters, so Google will cut it off around 60: “SULE76 – Esports Tech Portal Pragmatic Play PG Soft & 20+ Provider Server Stabil”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“SULE76 ⚡ Portal Game Online Terlengkap dari Provi…” and “SULE76 – Portal Game Online Terlengkap dengan Kol…”). One clear main headline is easier for people and search engines.

  • Meta description is long (223 characters)

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

  • 29 internal links, 10 external

    The homepage links to 29 pages on movexpk.com and 10 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://www.journeedelanonviolence.org/.

  • Structured data in place

    Structured data found: BreadcrumbList, MobileApplication 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.journeedelanonviolence.org/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.

  • No llms.txt

    There is no /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

    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 (1,216 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix93
  • 2 pages share a title

    /paris.php and / all use the title “SULE76 – Esports Tech Portal Pragmatic Play PG Soft & 20+ Provider Se…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 internal page checked

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

6 checks passed
  • Linked pages load

    All 1 page 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 1 page that loaded have a meta description.

  • 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 1 page 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 “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

2 to fix86
  • No HSTS header

    No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

  • No Content-Security-Policy

    No Content-Security-Policy header, the main browser-side defence against injected scripts.

  • No clickjacking protection

    Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

  • No X-Content-Type-Options

    X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

5 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (journeedelanonviolence.org).

  • Valid certificate (59 days left)

    The certificate from Let's Encrypt · YE1 verifies for movexpk.com and is valid for another 59 days.

  • http:// redirects to https

    http://movexpk.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 5 links work

    All 5 links checked from your homepage (1 internal, 4 external) answered without errors.

Domain and trust

  • No CAA record

    journeedelanonviolence.org has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

  • DNSSEC is off

    journeedelanonviolence.org's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

2 checks passed
  • Domain is 7 months old

    7 months

    journeedelanonviolence.org was registered in Mar 2026 through WhatIsYourDomain LLC. An established domain carries more trust with email providers and search engines.

  • Registered until Mar 2027

    journeedelanonviolence.org is registered until Mar 2027.

Content and conversion

2 to fix75
  • 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 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 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 1,209 words of copy

    The homepage carries about 1,209 words of visible text.

4 checks passed
  • 1 call to action

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

  • 1 short form

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

  • Social proof on the page

    Social proof on the homepage: 55 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Email authentication

2 to fix0
  • No DMARC policy

    movexpk.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

  • No SPF record

    movexpk.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

  • No DKIM key on the usual selectors

    We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

  • Domain receives no email

    movexpk.com has no MX record, so it receives no email. SPF -all and DMARC reject still matter: they stop others sending mail as you.

  • Email authentication score: 0/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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.

  • 7 other companies contacted

    Loading the homepage contacts 7 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).

Upkeep, stack and company

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

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

Go beyond the website

What your $25 Growth Playbook adds

This free review found 31 issues on movexpk.com, including 11 speed issues, 3 SEO issues and 2 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