Spain · Madrid Completed: Apr 21, 2026 19:22 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 75 / 100
Based on 8 categories, 0 sections
Decent speed, but optimizing further could improve engagement.
Several missing protections leave your users and data exposed.
Mostly accessible, but some users still face barriers.
Solid SEO basics — a few optimizations could boost rankings.
Solid infrastructure — fast server responses across the board.
Strong compliance posture across regulations.
Rich content metadata — your pages look great everywhere.
Heavier than average — reducing page weight saves energy and bandwidth.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
Cookie 'tid' is missing the Secure flag
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
No H1 heading found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/17f9f3d7-0803-4173-a292-146b6ea1b443)<a href="https://beavercheck.com/results/17f9f3d7-0803-4173-a292-146b6ea1b443"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fsemanticscholar.org" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fsemanticscholar.orgThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Addressing the critical issues below would have the most immediate impact on your user trust.
7 barrier(s) likely increasing bounce by ~29%.
Page takes 4.8s to load
+12% bounceUsers abandon at ~3s — you're 2.3s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 2.5s
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
No structured data
+2% bounceNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
Thin content
+3% bounceUnder 300 words — visitors bounce looking for substance, search engines rank competitors first
Fix: Add a substantive FAQ, product detail, or case-study section
Content is hard to read
+2% bounceGraduate-level reading difficulty — limits the addressable audience for product or blog pages
Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
€298 investment → €2,946/month returns + EUR 500,000 risk avoided
€298
4h · 5 findings
€2,946 /mo
~€35,353 / year
EUR 500,000
if kept compliant
€170 — in quick wins — start here for the fastest payback
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
3.5 developer hours at €85/hr
Based on European Union rates (€85/hr)
Start here for the best return on investment
€41,667 / month at risk
~€500,007 / year if left unfixed
€500,000
€0.56 /mo
7528.2 MB/mo × 0.074 EUR/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
3.62 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
4.78 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
2.55 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.001
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.62 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
19.57 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| cdn.semanticscholar.org/bc669961c407e17a/css/mobile.css | 72.1 KiB | 1.2 s |
| /css?family=Roboto+Slab:400,500,600,700|Roboto:300,400,50... | 2.5 KiB | 819 ms |
| fast.appcues.com/87350.js | 6.2 KiB | 752 ms |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| js.hs-analytics.net/analytics/1776798900000/5910970.js | 300.0 s | 42.3 KiB |
| js.hubspot.com/web-interactives-embed.js | 600.0 s | 28.2 KiB |
| js.hs-banner.com/v2/5910970/banner.js | 300.0 s | 24.1 KiB |
| fast.appcues.com/87350.js | 120.0 s | 6.2 KiB |
| js.hsadspixel.net/pixels.js | 600.0 s | 3.9 KiB |
| js.hs-scripts.com/5910970.js | 90.0 s | 1.1 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| semanticscholar.org/ | 939 ms |
| www.semanticscholar.org/ | 0.0 ms |
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| cdn.semanticscholar.org/bc669961c407e17a/css/mobile.css | 71.6 KiB | 69.2 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| cdn.semanticscholar.org/bc669961c407e17a/js/BrowserEntry.tsx.js | 707.6 KiB | 396.1 KiB |
| c09bc9c04079.edge.sdk.awswaf.com/c09bc9c04079/4996efde3854/challenge.js | 500.9 KiB | 256.5 KiB |
| www.googletagmanager.com/gtag/js?id=AW-936736651&cx=c>m=4e64h1 | 141.6 KiB | 103.1 KiB |
| /generic/main/7.20.2/appcues.main.6a6a274575024b516c91cfd... | 100.5 KiB | 72.5 KiB |
| accounts.google.com/gsi/client | 95.6 KiB | 71.9 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-592W6WL | 155.2 KiB | 70.9 KiB |
| www.googletagmanager.com/gtag/js?id=G-H7P4ZT52H5 | 177.0 KiB | 64.5 KiB |
| www.googletagmanager.com/gtag/js?id=AW-936736651 | 141.6 KiB | 53.8 KiB |
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| cdn.semanticscholar.org/bc669961c407e17a/js/BrowserEntry.tsx.js | 1.2 s | 966 ms | 248 ms |
| c09bc9c04079.edge.sdk.awswaf.com/c09bc9c04079/4996efde3854/challenge.js | 1.2 s | 985 ms | 102 ms |
| js.hs-analytics.net/analytics/1776798900000/5910970.js | 486 ms | 341 ms | 8.4 ms |
| Unattributable | 463 ms | 35 ms | 0.0 ms |
| /generic/main/7.20.2/appcues.main.6a6a274575024b516c91cfd... | 375 ms | 333 ms | 36 ms |
| www.semanticscholar.org/ | 342 ms | 16 ms | 13 ms |
| www.googletagmanager.com/gtag/js?id=G-H7P4ZT52H5 | 336 ms | 286 ms | 47 ms |
| www.googletagmanager.com/gtm.js?id=GTM-592W6WL | 237 ms | 198 ms | 36 ms |
| www.googletagmanager.com/gtag/js?id=AW-936736651 | 236 ms | 201 ms | 33 ms |
| js.hubspot.com/web-interactives-embed.js | 114 ms | 102 ms | 9.3 ms |
| www.googletagmanager.com/gtag/js?id=AW-936736651&cx=c>m=4e64h1 | 58 ms | 21 ms | 37 ms |
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 3.5 s |
| Script Parsing & Compilation | 611 ms |
| Other | 525 ms |
| Style & Layout | 322 ms |
| Garbage Collection | 92 ms |
| Parse HTML & CSS | 81 ms |
| Rendering | 38 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages with WebSocket cannot enter back/forward cache. | Pending browser support |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
| Back/forward cache is disabled because WebSocket has been used. | Not actionable |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Blog
(opens in a new tab) div.container > div.about-us__link-group > div.about-us__link-list > a.flex-row |
Ai2 Careers
(opens in a new tab) div.container > div.about-us__link-group > div.about-us__link-list > a.flex-row |
API Documentation
(opens in a new tab) div.container > div.about-us__link-group > div.about-us__link-list > a.flex-row |
Publications
(opens in a new tab) div.container > div.about-us__link-group > div.about-us__link-list > a.flex-row |
Research Careers
(opens in a new tab) div.container > div.about-us__link-group > div.about-us__link-list > a.flex-row |
Resources
(opens in a new tab) div.container > div.about-us__link-group > div.about-us__link-list > a.flex-row |
Terms of Service
(opens in a new tab) div.container > div > div.footer__row > a.tos-link |
Privacy Policy
(opens in a new tab) div.container > div > div.footer__row > a.pp-link |
The Allen Institute for AI
(opens in a new tab) footer.footer > section.page-section > div.container > a.footer-ai2-logo |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. | cdn.semanticscholar.org/bc669961c407e17a/js/BrowserEntry.tsx.js line 264, col 169460 |
| AttributionReporting | www.googletagmanager.com/gtag/js?id=AW-936736651 line 584, col 244 |
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
cdn.semanticscholar.org/bc669961c407e17a/js/BrowserEntry.tsx.js line 120, col 876168 | ERROR s2-client: attempted to use Heap before the global was set |
Not signed in with the identity provider. |
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| www.semanticscholar.org/product/semantic-reader | Learn More |
| www.semanticscholar.org/about | Learn More |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.45 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.55 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
411 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.45 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
4.22 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| cdn.semanticscholar.org/bc669961c407e17a/css/main.css | 82.1 KiB | 381 ms |
| /css?family=Roboto+Slab:400,500,600,700|Roboto:300,400,50... | 2.5 KiB | 269 ms |
| fast.appcues.com/87350.js | 6.2 KiB | 202 ms |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| js.hs-analytics.net/analytics/1776798900000/5910970.js | 300.0 s | 42.3 KiB |
| js.hubspot.com/web-interactives-embed.js | 600.0 s | 28.2 KiB |
| js.hs-banner.com/v2/5910970/banner.js | 300.0 s | 24.1 KiB |
| fast.appcues.com/87350.js | 120.0 s | 6.2 KiB |
| js.hsadspixel.net/pixels.js | 600.0 s | 3.9 KiB |
| js.hs-scripts.com/5910970.js | 90.0 s | 1.1 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| semanticscholar.org/ | 388 ms |
| www.semanticscholar.org/ | 0.0 ms |
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| cdn.semanticscholar.org/bc669961c407e17a/css/main.css | 81.7 KiB | 79.5 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| cdn.semanticscholar.org/bc669961c407e17a/js/BrowserEntry.tsx.js | 707.6 KiB | 396.1 KiB |
| c09bc9c04079.edge.sdk.awswaf.com/c09bc9c04079/4996efde3854/challenge.js | 501.0 KiB | 256.6 KiB |
| www.googletagmanager.com/gtag/js?id=AW-936736651&cx=c>m=4e64h1 | 141.6 KiB | 103.1 KiB |
| /generic/main/7.20.2/appcues.main.6a6a274575024b516c91cfd... | 100.5 KiB | 72.5 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-592W6WL | 155.2 KiB | 70.9 KiB |
| accounts.google.com/gsi/client | 95.6 KiB | 68.4 KiB |
| www.googletagmanager.com/gtag/js?id=G-H7P4ZT52H5 | 177.0 KiB | 64.5 KiB |
| www.googletagmanager.com/gtag/js?id=AW-936736651 | 141.6 KiB | 53.8 KiB |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages with WebSocket cannot enter back/forward cache. | Pending browser support |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
| Back/forward cache is disabled because WebSocket has been used. | Not actionable |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Search form#search-form > div.flex-row-vcenter > div.flex-row-vcenter > button.form-submit |
Blog
(opens in a new tab) div.container > div.about-us__link-group > div.about-us__link-list > a.flex-row |
Ai2 Careers
(opens in a new tab) div.container > div.about-us__link-group > div.about-us__link-list > a.flex-row |
API Documentation
(opens in a new tab) div.container > div.about-us__link-group > div.about-us__link-list > a.flex-row |
Publications
(opens in a new tab) div.container > div.about-us__link-group > div.about-us__link-list > a.flex-row |
Research Careers
(opens in a new tab) div.container > div.about-us__link-group > div.about-us__link-list > a.flex-row |
Resources
(opens in a new tab) div.container > div.about-us__link-group > div.about-us__link-list > a.flex-row |
Terms of Service
(opens in a new tab) div.container > div > div.footer__row > a.tos-link |
Privacy Policy
(opens in a new tab) div.container > div > div.footer__row > a.pp-link |
The Allen Institute for AI
(opens in a new tab) footer.footer > section.page-section > div.container > a.footer-ai2-logo |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. | cdn.semanticscholar.org/bc669961c407e17a/js/BrowserEntry.tsx.js line 264, col 169460 |
| AttributionReporting | www.googletagmanager.com/gtag/js?id=AW-936736651 line 584, col 244 |
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
accounts.google.com/gsi/client line 85, col 88 | [GSI_LOGGER]: FedCM get() rejects with NetworkError: Error retrieving a token. |
cdn.semanticscholar.org/bc669961c407e17a/js/BrowserEntry.tsx.js line 120, col 876168 | ERROR s2-client: attempted to use Heap before the global was set |
Not signed in with the identity provider. |
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| www.semanticscholar.org/product/semantic-reader | Learn More |
| www.semanticscholar.org/about | Learn More |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback