Website review, no card needed

giphy.com logo

giphy.com website review

Visit site (opens in a new tab)Reviewed 11 October 202633 issues · 81 checks

This review found 33 issues worth fixing on giphy.com, 10 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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.2 s1.9 sApr 18Oct 32.1 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20262.0 s
Apr 25, 20262.0 s
May 2, 20262.0 s
May 9, 20262.0 s
May 16, 20262.0 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
336 ms136 msApr 18Oct 3273 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026159 ms
Apr 25, 2026161 ms
May 2, 2026162 ms
May 9, 2026163 ms
May 16, 2026161 ms
May 23, 2026161 ms
May 30, 2026161 ms
Jun 6, 2026162 ms
Jun 13, 2026164 ms
Jun 20, 2026164 ms
Jun 27, 2026165 ms
Jul 4, 2026164 ms
Jul 11, 2026162 ms
Jul 18, 2026161 ms
Jul 25, 2026163 ms
Aug 1, 2026171 ms
Aug 8, 2026181 ms
Aug 15, 2026193 ms
Aug 22, 2026210 ms
Aug 29, 2026245 ms
Sep 5, 2026278 ms
Sep 12, 2026306 ms
Sep 19, 2026313 ms
Sep 26, 2026286 ms
Oct 3, 2026273 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 giphy.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. giphy.com at 0.5 s0.5 s
  2. giphy.com at 1.0 s1.0 s
  3. giphy.com at 1.5 s1.5 s
  4. giphy.com at 2.0 s2.0 s
  5. giphy.com at 2.5 s2.5 s
  6. giphy.com at 3.1 s3.1 s
  7. giphy.com at 3.6 s3.6 s
  8. giphy.com at 4.1 s4.1 s

Speed

7 to fix65
  • Reduce unused JavaScript

    2.6 s · 524 KiB

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

  • Use efficient cache lifetimes

    2.3 s · 625 KiB

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

  • Mobile performance score: 65

    65/100

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

  • Render-blocking requests

    750 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Didomi and others), adding 914 KiB and 557 ms of main-thread time.

  • Google Tag Manager adds 264 ms

    264 ms

    Google Tag Manager costs a phone 264 ms of main-thread work and 349 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.

  • Didomi adds 99 ms

    99 ms

    Didomi costs a phone 99 ms of main-thread work and 335 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.

  • 8 long tasks on the main thread

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

  • Legacy JavaScript

    25 KiB

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

  • Reduce unused CSS

    16 KiB

    About 16 KiB of CSS is downloaded but never applied on this page.

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

  • Duplicated JavaScript

    5 KiB

    5 KiB JavaScript is shipped twice across bundles.

2 checks passed
  • Main-thread work: 1.6 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

7 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: 24.0 s

    24.0 s

    Your largest element takes 24.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “GIPHY and our partners use cookies or similar technologies …”.

  • Time to Interactive: 25.2 s

    25.2 s

    The page becomes fully interactive after 25.2 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.

  • Real-user INP: 228 ms

    228 ms

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

  • Tap response (INP) got 75% slower for real visitors

    +75%

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

  • Total Blocking Time: 231 ms

    231 ms

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

6 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user CLS: 0.06

    0.06

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 691 ms

    691 ms

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, 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.

Images and page weight

2 to fix55
  • Page weight: 4.9 MB in 96 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 96 requests on a phone: images 3.3 MB (17), scripts 1.5 MB (50) and fonts 132 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 2.8 MB together. On a phone connection a single image that size takes seconds.

  • About 1.4 g of CO₂ per visit

    1.40 g

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

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

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 9393
  • All page content should be contained by landmarks (25 elements)

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

  • Zoom is disabled

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

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 30 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 34 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 passed and 4 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 9287
  • Title is short (19 characters)

    Your title is only 19 characters: “GIPHY - Be Animated”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No XML sitemap

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

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 36 internal links, 1 external

    The homepage links to 36 pages on giphy.com and 1 external page.

6 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “GIPHY is the platform that animates your world. Find the GIFs, Clips, and Stickers that make your conversations more po…”.

  • One H1 headline

    Your main headline reads: “Trending Now”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: WebPage.

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

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    24%

    A phone browser shows 196 words, but the HTML your server sends has only 47. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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://giphy.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.

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

4 to fix79
  • 2 linked pages hidden from search

    https://giphy.com/gifs/lol-grammys-steven-tyler-BFYLNwlsSNtcc and https://giphy.com/gifs/cowboys-steelers-pittsburgh-HXktDkGLHbM1a are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 3 pages share a title

    https://giphy.com/gifs/green-bay-packers-go-pack-S3qpvaeP7qVxPiSdft, https://giphy.com/gifs/green-bay-packers-go-pack-aoGHHC3JzhgxtUWMzf and https://giphy.com/gifs/green-bay-packers-go-pack-egShSV6u6SebpixXEG all use the title “Green Bay Packers GIF - Find & Share on GIPHY”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages share a meta description

    https://giphy.com/gifs/green-bay-packers-go-pack-S3qpvaeP7qVxPiSdft, https://giphy.com/gifs/green-bay-packers-go-pack-aoGHHC3JzhgxtUWMzf and https://giphy.com/gifs/green-bay-packers-go-pack-egShSV6u6SebpixXEG use the same meta description. A description written for each page earns more clicks.

  • 12 pages without an H1

    https://giphy.com/gifs/green-bay-packers-go-pack-S3qpvaeP7qVxPiSdft, https://giphy.com/gifs/lol-grammys-steven-tyler-BFYLNwlsSNtcc, https://giphy.com/gifs/patriots-pats-go-patriots-y953AaDqaxd2Nkk6OV, https://giphy.com/gifs/GYDb4HjCuJbUDGCznU, https://giphy.com/gifs/cowboys-steelers-pittsburgh-HXktDkGLHbM1a and https://giphy.com/gifs/onmilwaukee-cheer-green-bay-handegg-RNDt37PN9Y1F83X47y and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 pages with very little text

    https://giphy.com/gifs/green-bay-packers-go-pack-S3qpvaeP7qVxPiSdft, https://giphy.com/gifs/patriots-pats-go-patriots-y953AaDqaxd2Nkk6OV, https://giphy.com/gifs/GYDb4HjCuJbUDGCznU, https://giphy.com/gifs/onmilwaukee-cheer-green-bay-handegg-RNDt37PN9Y1F83X47y, https://giphy.com/gifs/nfl-sports-football-sport-GWPoLZEFhy0vrnlQpp and https://giphy.com/gifs/steelers-celebration-celebrate-dab-VWOecPr1OhEUJU48wZ 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.

  • 12 internal pages checked

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

4 checks passed
  • Linked pages load

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

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

Google 96100
  • 7 low-resolution images

    7 images are served at too low a resolution for sharp phone screens.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Only about 196 words

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Try our App”.

  • 1 call to action

    The homepage has 1 call to action, for example “Try our App”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Comscore, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies (measured from a US location before any click).

  • 10 other companies contacted

    Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Didomi

    A consent management tool (Didomi) loads with the page.

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 giphy.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Tag Manager

Company

Founded
2013

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on giphy.com, including 14 speed issues, 3 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