Website review, no card needed

1688d2d.com logo

1688d2d.com website review

Visit site (opens in a new tab)Reviewed 16 November 202649 issues · 82 checks

This review found 49 issues worth fixing on 1688d2d.com, 27 of them high impact, across 82 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 1688d2d.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 1688d2d.com at 1.8 s1.8 s
  2. 1688d2d.com at 3.5 s3.5 s
  3. 1688d2d.com at 5.3 s5.3 s
  4. 1688d2d.com at 7.1 s7.1 s
  5. 1688d2d.com at 8.9 s8.9 s
  6. 1688d2d.com at 10.6 s10.6 s
  7. 1688d2d.com at 12.4 s12.4 s
  8. 1688d2d.com at 14.2 s14.2 s

Speed

13 to fix28
  • Render-blocking requests

    10.2 s

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

  • Improve image delivery

    3.1 s · 6.5 MB

    27 images could be 6.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.1 s faster on a phone.

  • Reduce unused JavaScript

    7.0 s · 2.0 MB

    About 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.0 s faster on a phone.

  • Use efficient cache lifetimes

    1.9 s · 944 KiB

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

  • Minify JavaScript

    1.8 s · 382 KiB

    382 KiB could be saved by minifying JavaScript.

  • yesourcing.com adds 1.4 s

    1.4 s

    yesourcing.com costs a phone 1.4 s of main-thread work and 4.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Google Tag Manager adds 1.0 s

    1.0 s

    Google Tag Manager costs a phone 1.0 s of main-thread work and 1.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 11.7 s

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

  • Mobile performance score: 28

    28/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (yesourcing.com, Google Tag Manager and Facebook and others), adding 7.1 MB and 2.9 s of main-thread time.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 476 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    300 ms · 55 KiB

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

  • Font display

    350 ms

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

  • Legacy JavaScript

    150 ms · 48 KiB

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

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

    42 ms

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

Core Web Vitals

6 to fix36
  • First Contentful Paint: 10.0 s

    10.0 s

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

  • Largest Contentful Paint: 29.1 s

    29.1 s

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

  • Time to Interactive: 44.1 s

    44.1 s

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

  • Speed Index: 11.9 s

    11.9 s

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

  • Total Blocking Time: 1.8 s

    1.8 s

    Scripts block taps and scrolling for 1.8 s in total while the page loads. Good is under 200 ms.

  • 48 images without width and height

    48 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
  • Cumulative Layout Shift: 0.032

    0.032

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

Images and page weight

5 to fix18
  • Page weight: 12.6 MB in 201 requests

    12.6 MB

    Your homepage downloads 12.6 MB in 201 requests on a phone: images 6.9 MB (54), scripts 5.2 MB (62) and fonts 180 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 25 images far larger than shown

    3.1 MB

    25 images are downloaded at several times the size a phone draws them, for example O1CN0142KSpq1loE0nXVhrH_!!6000000004865-0-cib.jpg at 1,920 px wide, shown at 170 px. Resized copies would save about 3.1 MB.

  • 1 image over 500 KB

    O1CN0142KSpq1loE0nXVhrH_!!6000000004865-0-cib.jpg weighs 674 KiB. On a phone connection a single image that size takes seconds.

  • 28 images in older formats

    28 images (7.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.

  • 20 images below the first screen load straight away

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

  • About 3.6 g of CO₂ per visit

    3.57 g

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

Accessibility

8 to fixGoogle 8086
  • 27 text elements with low contrast

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

  • 3 tap targets too small

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

  • 1 image without alt text

    1 image has 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.

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

  • 6 links without text

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

  • 2 form fields without a label

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

1 checks passed
  • 32 automated accessibility rules passed

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

6 to fixGoogle 6158
  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • No H1 headline

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

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • 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 (182 characters)

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

  • No XML sitemap

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

  • 100 internal links, 6 external

    The homepage links to 100 pages on 1688d2d.com and 6 external pages.

3 checks passed
  • Title: 51 characters

    Your title is a healthy 51 characters: “1688d2d - Dropshipping from Worldwide to Worldwide!”.

  • Canonical URL set

    The canonical URL is https://1688d2d.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

2 to fix53
  • robots.txt blocks 6 AI answer engine crawlers

    6 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

1 checks passed
  • Text is in the HTML

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

Other pages

3 to fix83
  • 15 pages share a title

    https://www.1688d2d.com/list/wholesale-womens-clothing-l-196997508.html, https://www.1688d2d.com/list/wholesale-mens-clothing-l-196997510.html, https://www.1688d2d.com/list/wholesale-kids-clothing-l-196997501.html, https://www.1688d2d.com/list/wholesale-underwears-l-196997509.html, https://www.1688d2d.com/list/wholesale-shoes-l-196997496.html and https://www.1688d2d.com/list/wholesale-accessories-l-196997518.html and 9 others all use the title “Human verification”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://www.1688d2d.com/list/wholesale-womens-clothing-l-196997508.html, https://www.1688d2d.com/list/wholesale-mens-clothing-l-196997510.html, https://www.1688d2d.com/list/wholesale-kids-clothing-l-196997501.html, https://www.1688d2d.com/list/wholesale-underwears-l-196997509.html, https://www.1688d2d.com/list/wholesale-shoes-l-196997496.html and https://www.1688d2d.com/list/wholesale-accessories-l-196997518.html and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.1688d2d.com/list/wholesale-womens-clothing-l-196997508.html, https://www.1688d2d.com/list/wholesale-mens-clothing-l-196997510.html, https://www.1688d2d.com/list/wholesale-kids-clothing-l-196997501.html, https://www.1688d2d.com/list/wholesale-underwears-l-196997509.html, https://www.1688d2d.com/list/wholesale-shoes-l-196997496.html and https://www.1688d2d.com/list/wholesale-accessories-l-196997518.html and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 pages with very little text

    https://www.1688d2d.com/list/wholesale-womens-clothing-l-196997508.html, https://www.1688d2d.com/list/wholesale-mens-clothing-l-196997510.html, https://www.1688d2d.com/list/wholesale-kids-clothing-l-196997501.html, https://www.1688d2d.com/list/wholesale-underwears-l-196997509.html, https://www.1688d2d.com/list/wholesale-shoes-l-196997496.html and https://www.1688d2d.com/list/wholesale-accessories-l-196997518.html and 9 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.

  • 5 pages slow to respond

    https://www.1688d2d.com/list/wholesale-kids-clothing-l-196997501.html, https://www.1688d2d.com/list/wholesale-underwears-l-196997509.html, https://www.1688d2d.com/list/wholesale-home-furniture-l-196997505.html, https://www.1688d2d.com/list/wholesale-skin-care-makeup-l-196997511.html and https://www.1688d2d.com/list/wholesale-luggage-bags-l-196997498.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 48 found) and read each the way a search engine does.

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

  • 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

2 to fixGoogle 9278
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=27034736&Ver=2&mid=ba4447ec-1a4e-418f-8b46-5e04f9c7bbde&bo=1&sid=daedd810e1e111f1a1f647ece565bd18&vid=daede290e1e111f1a332cb415cbd1fb8&vids=1&msclkid=N&pi=918639831&lg.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

  • Requests the notification permission on page load

    Requests the notification permission on page load.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • About 665 words of copy

    The homepage carries about 665 words of visible text.

2 checks passed
  • 1 call to action

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and TikTok Pixel.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 27 cookies set on arrival

    27

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

  • 27 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
Alibaba Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on 1688d2d.com, including 19 speed issues, 6 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