api.de website review

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

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

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

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

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

skynettechnologies.com costs a phone 11 ms of main-thread work and 515 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.

2 KiB could be saved by minifying CSS.

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

1 third-party service load with your homepage (skynettechnologies.com), adding 515 KiB and 11 ms of main-thread time.

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

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

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

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

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

Your largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Bei uns sind Sie genau richtig, wenn Sie von 30 Jahren Erfa…”. Most of its time is element render delay (5.4 s).

Icy_Box_color_logo.png weighs 749 KiB. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example Icy_Box_color_logo.png at 19,357 px wide, shown at 140 px. Resized copies would save about 928 KiB.

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

4 images (1.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.

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

5 elements have a tabindex above 0, which scrambles the keyboard order.

autocomplete attribute must be used correctly: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

1 link inside paragraphs relies on colour alone to stand out.

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

Your title is only 15 characters: “api GmbH - Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your canonical URL points to api2022.api.de, not api.de, so Google may credit that host instead.

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://api.de/index.php/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 65 pages on api.de and 69 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 /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.

/ and /en all use the title “api GmbH - Home”. Search engines can't tell which page to show for a search, so each competes with the others.

/newsletteranmeldung and /mehrwerte/nachhaltig-it-1 have no meta description, so Google writes the search snippet from whatever text it finds.

/unternehmen, /unternehmen/profil, /unternehmen/standort, /newsletteranmeldung, /mehrwerte/build-to-order and /mehrwerte/shop2go and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

/financial-services took over 3 s to send its HTML from our server.

We fetched 15 pages linked from your homepage (of 49 found) and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 link from your homepage to your own site is broken, for example https://api.de/3cx.old/index.html (404).

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

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

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

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

2 links go through two or more redirects, for example https://api.de/mehrwerte/financial-services.

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

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

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

api.de 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.

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 736 words of visible text.

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.

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.

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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.