parissaasweek.com website review

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

26 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

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

7 third-party services load with your homepage (website-files.com, sibforms.com and Google Tag Manager and others), adding 3.8 MB and 206 ms of main-thread time.

website-files.com costs a phone 86 ms of main-thread work and 3.3 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.

The page has 2,224 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

About 245 KiB of JavaScript is downloaded but never used on this page.

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

4 KiB could be saved by minifying CSS.

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

52 images have no width and height attributes, so the layout jumps as each one loads.

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

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

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.

Your homepage downloads 3.9 MB in 65 requests on a phone: images 2.8 MB (43), scripts 526 KiB (9) and fonts 510 KiB (7). Under 2 MB keeps phones on slow connections fast.

65a52335ab809ac16450cd21_Paris-header-p-500.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

8 images (680 KiB) 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.

2 images are downloaded at several times the size a phone draws them, for example 66d189887464f2764d9dc674_women of saas.png at 500 px wide, shown at 100 px. Resized copies would save about 87 KiB.

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

All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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

Your title is only 28 characters: “Paris SaaS Week by B2B Rocks”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 7 <h1> headlines (“Subscribe to our Newsletter”, “Once a month or so we will send updates on ARRtis…” and “Paris SaaS Week, happening from September 23 to S…”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

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

The homepage links to 5 pages on parissaasweek.com and 158 external pages.

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.

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

https://www.parissaasweek.com/condition and https://www.parissaasweek.com/privacy all use the title “Privacy”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.parissaasweek.com/condition, https://www.parissaasweek.com/privacy and https://www.parissaasweek.com/imprint have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.parissaasweek.com/imprint has 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.

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

10 images failed to load on a phone, for example https://www.parissaasweek.com/.

4 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://sibforms.com/forms/end-form/build/sib-styles.css' from origin 'https://www.parissa…”.

Large scripts ship without source maps.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 714 words of visible text.

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.

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

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.

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