HTTPS://www.pearreview.com
Lighthouse Mobile
· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0
Detailed Report
Audit breakdown by category with detailed findings.
55
Performance
Insights
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Why this matters
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
Why this matters
Performance issues directly impact user engagement and conversion rates.
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Why this matters
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Why this matters
Performance issues directly impact user engagement and conversion rates.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Why this matters
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.
Why this matters
Performance issues directly impact user engagement and conversion rates.
headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:0.568 source:map[column:356 line:423 type:source-location url:https://pagead2.googlesyndication.com/pagead/managed/js/adsense/m202608200101/show_ads_impl_fy2021.js?bust=122880588 urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:38.918 source:map[type:text value:[unattributed]]] map[reflowTime:0.568 source:map[column:324 line:732 type:source-location url:https://pagead2.googlesyndication.com/pagead/managed/js/adsense/m202608200101/show_ads_impl_fy2021.js?bust=122880588 urlProvider:network]]]
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Why this matters
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
body.front > div#page > div#page-inner > div#header body.front > div#page > div#page-inner > div#header | www.pearreview.com/sites/all/themes/PearReview/images/haeder.jpg | 84.8 KiB | 47.6 KiB |
Startseite
Features
Download
Impressum
Kontakt
Video Tutorial
News
Systemanford… div#page-inner > div#main > div#main-inner > div#navbar | www.pearreview.com/sites/all/themes/PearReview/images/menu.jpg | 28.4 KiB | 22.6 KiB |
| www.pearreview.com/sites/all/themes/PearReview/images/background.jpg | 11.5 KiB | 11.4 KiB | |
div.content > form#user-login-form > div > input#edit-submit div.content > form#user-login-form > div > input#edit-submit | www.pearreview.com/sites/all/themes/PearReview/images/btn_back.jpg | 11.0 KiB | 11.0 KiB |
Copyright © 2015 PearReview -- All rights reserved.
Startseite
Features
Downloa… body.front > div#page > div#page-inner > div#footer | www.pearreview.com/sites/all/themes/PearReview/images/footer.jpg | 21.2 KiB | 6.4 KiB |
Download div.node-inner > div.content > p > a.pdf | www.pearreview.com/sites/all/themes/PearReview/images/pdf.png | 4.2 KiB | 4.0 KiB |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Why this matters
Performance issues directly impact user engagement and conversion rates.
lhId: page-0-DIV
nodeLabel: body.front > div#page > div#page-inner > div#header
path: 0,HTML,1,BODY,30,DIV,0,DIV,1,DIV
selector: body.front > div#page > div#page-inner > div#header
snippet: <div id="header">
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.
Why this matters
Performance issues directly impact user engagement and conversion rates.
description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
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.
Why this matters
Performance issues directly impact user engagement and conversion rates.
Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.
Why this matters
Performance issues directly impact user engagement and conversion rates.
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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.
Why this matters
Performance issues directly impact user engagement and conversion rates.
TTI
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.
Why this matters
Performance issues directly impact user engagement and conversion rates.
Diagnostics
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Why this matters
Performance issues directly impact user engagement and conversion rates.
Estimated savings: 0.0 ms 3.8 KiB
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.pearreview.com/sites/all/themes/PearReview/style-G.css | 6.0 KiB | 3.8 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.
Why this matters
Performance issues directly impact user engagement and conversion rates.
Estimated savings: 1.8 s 205.4 KiB
| URL | Transfer Size | Est Savings |
|---|---|---|
| /pagead/managed/js/adsense/m202608200101/show_ads_impl_fy... | 162.2 KiB | 109.9 KiB |
| /pagead/js/adsbygoogle.js?client=ca-pub-1502173011299631 | 55.8 KiB | 45.7 KiB |
| /pagead/js/adsbygoogle.js?client=ca-pub-1502173011299631 | 55.8 KiB | 27.0 KiB |
| www.pearreview.com/sites/all/themes/PearReview/js/jquery-G.js | 36.4 KiB | 22.9 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.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| /pagead/managed/js/adsense/m202608200101/show_ads_impl_fy... | 779 ms | 628 ms | 126 ms |
| www.pearreview.com/ | 476 ms | 12 ms | 6.2 ms |
| Unattributable | 445 ms | 11 ms | 0.0 ms |
| /pagead/js/adsbygoogle.js?client=ca-pub-1502173011299631 | 302 ms | 215 ms | 73 ms |
| www.pearreview.com/sites/all/themes/PearReview/js/jquery-G.js | 120 ms | 90 ms | 14 ms |
| ep2.adtrafficquality.google/sodar/sodar2.js | 66 ms | 58 ms | 3.7 ms |
| www.pearreview.com/misc/jquery-G.js | 56 ms | 50 ms | 5.0 ms |
| www.pearreview.com/misc/drupal-G.js | 53 ms | 46 ms | 1.7 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
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 1.2 s |
| Other | 606 ms |
| Style & Layout | 278 ms |
| Script Parsing & Compilation | 236 ms |
| Rendering | 68 ms |
| Parse HTML & CSS | 62 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
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Why this matters
Performance issues directly impact user engagement and conversion rates.
Estimated savings: 0.0 ms 19.7 KiB
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.pearreview.com/sites/all/themes/PearReview/js/jquery-G.js | 36.4 KiB | 14.5 KiB |
| www.pearreview.com/sites/all/themes/PearReview/js/jquery.lightbox-0.5-G.js | 5.5 KiB | 2.9 KiB |
| www.pearreview.com/misc/drupal-G.js | 3.6 KiB | 2.4 KiB |
More information about the performance of your application. These numbers don't directly affect the Performance score.
●Layout shift culprits
●Document request latency
●Optimize DOM size
●LCP breakdown
●Modern HTTP
●Reduce unused CSS
●Avoids enormous network payloads Total size was 627 KiB
●Avoid long main-thread tasks 8 long tasks found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 480 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 330 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
95
Accessibility
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.
Best practices
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
http://en.wikipedia.org/wiki/Software_inspection div.node-inner > div.content > p > a |
http://en.wikipedia.org/wiki/Software_peer_review div.node-inner > div.content > p > a |
http://en.wikipedia.org/wiki/Peer_review div.node-inner > div.content > p > a |
Deutsch div.content > ul > li.de > a.language-link |
English div.content > ul > li.en > a.language-link |
Русский div.content > ul > li.ru > a.language-link |
News div.content > ul.menu > li.leaf > a |
div.content > form#user-login-form > div > input#edit-submit div.content > form#user-login-form > div > input#edit-submit |
Registrieren div.item-list > ul > li.first > a |
Neues Passwort anfordern div.item-list > ul > li.last > a |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html.js html.js |
These items highlight common accessibility best practices.
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Input buttons have discernible text.
●Form elements have associated labels
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○Buttons have an accessible name
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○Image elements have `[alt]` attributes
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
50
Best Practices
Trust and Safety
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Insecure URL | Request Resolution |
|---|---|
| pearreview.com/ | Blocked |
Browser Compatibility
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Why this matters
Performance issues directly impact user engagement and conversion rates.
General
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. |
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
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Mixed Content: The page at 'https://www.pearreview.com/' was loaded over HTTPS, but requested an insecure favicon 'http://pearreview.com/'. This request has been blocked; the content must be served over HTTPS. |
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Mixed content |
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Properly defines charset
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
82
SEO
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.
Content Best Practices
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Why this matters
Performance issues directly impact user engagement and conversion rates.
Format your HTML in a way that enables crawlers to better understand your app’s content.
Crawling and Indexing
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Line # | Content | Error |
|---|---|---|
| 1 | <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1502173011299631" | Unknown directive |
| 2 | crossorigin="anonymous"></script><center> | Syntax not understood |
| 3 | <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1502173011299631" | Unknown directive |
| 4 | crossorigin="anonymous"></script> | Syntax not understood |
| 5 | <!-- erge444 --> | Syntax not understood |
| 6 | <ins class="adsbygoogle" | Syntax not understood |
| 7 | style="display:block" | Unknown directive |
| 8 | data-ad-client="ca-pub-1502173011299631" | Syntax not understood |
| 9 | data-ad-slot="7009662871" | Syntax not understood |
| 10 | data-ad-format="auto" | Syntax not understood |
| 11 | data-full-width-responsive="true"></ins> | Syntax not understood |
| 12 | <script> | Syntax not understood |
| 13 | (adsbygoogle = window.adsbygoogle || []).push({}); | Syntax not understood |
| 14 | </script> | Syntax not understood |
| 15 | </center> | Syntax not understood |
| 16 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> | Unknown directive |
| 17 | <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="de" lang="de" dir="ltr"> | Unknown directive |
| 18 | <head> | Syntax not understood |
| 19 | <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> | Syntax not understood |
| 20 | <title>Startseite | PearReview - Review-Tool</title> | Syntax not understood |
| 21 | <link rel="canonical" href="https://pearreview.com" /> | Unknown directive |
| 22 | <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> | Syntax not understood |
| 23 | <link rel="shortcut icon" href="sites/all/themes/PearReview/favicon.ico" type="image/x-icon"/> | Syntax not understood |
| 24 | <link type="text/css" rel="stylesheet" media="all" href="modules/node/node-G.css"/> | Syntax not understood |
| 25 | <link type="text/css" rel="stylesheet" media="all" href="modules/poll/poll-G.css"/> | Syntax not understood |
| 26 | <link type="text/css" rel="stylesheet" media="all" href="modules/system/defaults-G.css"/> | Syntax not understood |
| 27 | <link type="text/css" rel="stylesheet" media="all" href="modules/system/system-G.css"/> | Syntax not understood |
| 28 | <link type="text/css" rel="stylesheet" media="all" href="modules/system/system-menus-G.css"/> | Syntax not understood |
| 29 | <link type="text/css" rel="stylesheet" media="all" href="modules/user/user-G.css"/> | Syntax not understood |
| 30 | <link type="text/css" rel="stylesheet" media="all" href="sites/all/themes/zen/zen/tabs-G.css"/> | Syntax not understood |
| 31 | <link type="text/css" rel="stylesheet" media="all" href="sites/all/themes/PearReview/messages-G.css"/> | Syntax not understood |
| 32 | <link type="text/css" rel="stylesheet" media="all" href="sites/all/themes/zen/zen/block-editing-G.css"/> | Syntax not understood |
| 33 | <link type="text/css" rel="stylesheet" media="all" href="sites/all/themes/zen/zen/wireframes-G.css"/> | Syntax not understood |
| 34 | <link type="text/css" rel="stylesheet" media="all" href="sites/all/themes/PearReview/zen-G.css"/> | Syntax not understood |
| 35 | <link type="text/css" rel="stylesheet" media="all" href="sites/all/themes/PearReview/layout-fixed-G.css"/> | Syntax not understood |
| 36 | <link type="text/css" rel="stylesheet" media="all" href="sites/all/themes/PearReview/style-G.css"/> | Syntax not understood |
| 37 | <link type="text/css" rel="stylesheet" media="all" href="sites/all/themes/PearReview/jquery.lightbox-0.5-G.css"/> | Syntax not understood |
| 38 | <!--[if IE]> | Syntax not understood |
| 39 | <link type="text/css" rel="stylesheet" media="all" href="/sites/all/themes/zen/zen/ie.css?G" /> | Syntax not understood |
| 40 | <![endif]--> | Syntax not understood |
| 41 | <script type="text/javascript" src="misc/jquery-G.js"></script> | Syntax not understood |
| 42 | <script type="text/javascript" src="misc/drupal-G.js"></script> | Syntax not understood |
| 43 | <script type="text/javascript" src="sites/default/files/languages/de_1ad018fc22722f19c63dba9334d35589-G.js"></script> | Syntax not understood |
| 44 | <script type="text/javascript" src="sites/all/themes/PearReview/js/jquery-G.js"></script> | Syntax not understood |
| 45 | <script type="text/javascript" src="sites/all/themes/PearReview/js/jquery.lightbox-0.5-G.js"></script> | Syntax not understood |
| 46 | <script type="text/javascript" src="sites/all/themes/PearReview/js/jquery.color-G.js"></script> | Syntax not understood |
| 47 | <script type="text/javascript"> | Syntax not understood |
| 48 | <!--//--><![CDATA[//><!-- | Syntax not understood |
| 49 | jQuery.extend(Drupal.settings, { "basePath": "/" }); | Unknown directive |
| 50 | //--><!]]> | Syntax not understood |
| 51 | </script> | Syntax not understood |
| 52 | <script type="text/javascript"> | Syntax not understood |
| 53 | $(document).ready(function(){ | Syntax not understood |
| 54 | //lightbox | Syntax not understood |
| 55 | var settings = { | Syntax not understood |
| 56 | imageLoading: 'http://www.pearreview.com/sites/all/themes/PearReview/images/lightbox-ico-loading.gif', | Unknown directive |
| 57 | imageBtnPrev: 'http://www.pearreview.com/sites/all/themes/PearReview/images/lightbox-btn-prev.gif', | Unknown directive |
| 58 | imageBtnNext: 'http://www.pearreview.com/sites/all/themes/PearReview/images/lightbox-btn-next.gif', | Unknown directive |
| 59 | imageBtnClose: 'http://www.pearreview.com/sites/all/themes/PearReview/images/lightbox-btn-close.gif', | Unknown directive |
| 60 | imageBlank: 'http://www.pearreview.com/sites/all/themes/PearReview/images/lightbox-blank.gif' | Unknown directive |
| 61 | }; | Syntax not understood |
| 62 | $("#content a[href$='.jpg']").lightBox(settings); | Syntax not understood |
| 63 | $("#content a[href$='.png']").lightBox(settings); | Syntax not understood |
| 64 | $("#content a[href$='.gif']").lightBox(settings); | Syntax not understood |
| 65 | $("#content a[href$='.jpeg']").lightBox(settings); | Syntax not understood |
| 66 | //animate input fields | Syntax not understood |
| 67 | var input = $("form input[class!=form-submit]"); | Syntax not understood |
| 68 | input.focus(function(){ | Syntax not understood |
| 69 | $(this).animate({backgroundColor: "#d9e880"}, "slow") | Unknown directive |
| 70 | }); | Syntax not understood |
| 71 | input.blur(function(){ | Syntax not understood |
| 72 | $(this).animate({backgroundColor: "#ffffff"}, "slow") | Unknown directive |
| 73 | }); | Syntax not understood |
| 74 | //animate textarea | Syntax not understood |
| 75 | var textarea = $("form textarea"); | Syntax not understood |
| 76 | textarea.focus(function(){ | Syntax not understood |
| 77 | $(this).animate({backgroundColor: "#d9e880"}, "slow") | Unknown directive |
| 78 | }); | Syntax not understood |
| 79 | textarea.blur(function(){ | Syntax not understood |
| 80 | $(this).animate({backgroundColor: "#ffffff"}, "slow") | Unknown directive |
| 81 | }); | Syntax not understood |
| 82 | // Add pdf icons to pdf links | Syntax not understood |
| 83 | $("a[href$='.pdf']").addClass("pdf"); | Syntax not understood |
| 84 | // Add exe icons to pdf links | Syntax not understood |
| 85 | $("a[href$='.exe']").addClass("exe"); | Syntax not understood |
| 86 | // Add dmg icons to pdf links | Syntax not understood |
| 87 | $("a[href$='.dmg']").addClass("dmg"); | Syntax not understood |
| 88 | // Add jar icons to pdf links | Syntax not understood |
| 89 | $("a[href$='.jar']").addClass("jar"); | Syntax not understood |
| 90 | // Add xml icons to pdf links | Syntax not understood |
| 91 | $("a[href$='.xml']").addClass("xml"); | Syntax not understood |
| 92 | // Add zip icons to pdf links | Syntax not understood |
| 93 | $("a[href$='.zip']").addClass("zip"); | Syntax not understood |
| 94 | }); | Syntax not understood |
| 95 | </script> | Syntax not understood |
| 96 | </head> | Syntax not understood |
| 97 | <body class="front not-logged-in node-type-page one-sidebar sidebar-right"> | Syntax not understood |
| 98 | <div id="page"><div id="page-inner"> | Syntax not understood |
| 99 | <a name="top" id="navigation-top"></a> | Syntax not understood |
| 100 | <div id="header"><div id="header-inner" class="clear-block"> | Syntax not understood |
| 101 | <div id="head_logo"><a class="logo_link" href="/" title="Startseite" rel="home"></a></div> | Syntax not understood |
| 102 | <div id="head_download"><a class="download_link" href="download" title="Download PearReview"></a></div> | Syntax not understood |
| 103 | <div class="clear"></div> | Syntax not understood |
| 104 | </div></div> <!-- /#header-inner, /#header --> | Syntax not understood |
| 105 | <div id="main"><div id="main-inner" class="clear-block with-navbar"> | Syntax not understood |
| 106 | <div id="content"><div id="content-inner"> | Syntax not understood |
| 107 | <div id="content-header"> | Syntax not understood |
| 108 | <h1 class="title">Startseite</h1> | Syntax not understood |
| 109 | </div> <!-- /#content-header --> | Syntax not understood |
| 110 | <div id="content-area"> | Syntax not understood |
| 111 | <div id="node-1" class="node node-type-page"><div class="node-inner"> | Syntax not understood |
| 112 | <div class="content"> | Syntax not understood |
| 113 | <p>PearReview ist ein Assistent zum Planen und Durchführen von Reviews. Unter einem Review wird hier speziell das technische Review im Software-Bereich (*) verstanden. PearReview lässt sich allerdings problemlos auch in anderen Bereichen einsetzten.</p> | Syntax not understood |
| 114 | <p>PearRview ist eine Open Source Software, die im Rahmen des Software-Praktikums an der Universität Stuttgart entstanden ist und kann kostenlos im privaten und kommerziellen Gebrauch eingesetzt werden.</p> | Syntax not understood |
| 115 | <p>PearReview unterstützt das Planen von Review-Sitzungen, erlaubt es den Teilnehmern bestimmte Rollen (Moderator, Notar, Gutachter, Autor und Kunde) zu zuweisen und schriftliche Einladungen in Form von PDF-Dokumenten für sie zu erstellen.<br/> | Syntax not understood |
| 116 | Es ist möglich den Gutachtern bestimmte Aspekte zu zuweisen, auf die sie den Prüfling untersuchen können. Aspekte können in XML-Form als Kataloge verwaltet und dadurch in mehreren Projekten verwendet werden.<br/> | Syntax not understood |
| 117 | Während der Review-Sitzung können Befunde mit PearReview in einem Protokoll notiert, verwaltet und exportiert werden. </p> | Syntax not understood |
| 118 | <p> <u>Nachtrag:</u> Das Projekt wurde gestern (24.07.2024) abgeschlossen und uns drängte sich die Frage auf, welche Zukunft PearReview einschlagen sollte. Daher haben wir (die Entwickler) einen einfachen Plan aus 2 Schritten ausgearbeitet, der das weitere Vorgehen bestimmen wird: </p> | Unknown directive |
| 119 | <ul> | Syntax not understood |
| 120 | <li>Schritt 1 - Wartung und Verbreitung | Syntax not understood |
| 121 | <ul> | Syntax not understood |
| 122 | <li>Korrektur bestehender Fehler</li> | Syntax not understood |
| 123 | <li>Verbesserung einiger Usability-Macken</li> | Syntax not understood |
| 124 | <li>Verbreitung von PearReview</li> | Syntax not understood |
| 125 | </ul> | Syntax not understood |
| 126 | </li> | Syntax not understood |
| 127 | <li>Schritt 2 - Erweiterung | Syntax not understood |
| 128 | <ul> | Syntax not understood |
| 129 | <li>Sammeln guter Ideen</li> | Syntax not understood |
| 130 | <li>Erweiterung der Funktionen</li> | Syntax not understood |
| 131 | </ul> | Syntax not understood |
| 132 | </li> | Syntax not understood |
| 133 | </ul> | Syntax not understood |
| 134 | <p> | Syntax not understood |
| 135 | Es ist daher auch eine neue Website in Planung, die die neuen Anforderungen (Bugtracking usw.) erfüllen kann. Unser Plakat aus der gestrigen Präsentation steht ebenfalls zum <a href="PearReview-Plakat.pdf">Download</a> bereit. Wir würden uns über <a href="kontakt">Feedback</a> sehr freuen.</p> | Syntax not understood |
| 136 | <p></p> | Syntax not understood |
| 137 | <p>* PearReview unterstützt die Vorgehensweise, die in "Ludewig, J. and Lichter, H. (2008): Software Engineering. dpunkt.verlag GmbH, ISBN 3-89864-268-2" beschrieben wird. Weiterführende Links zu Reviews:</p> | Unknown directive |
| 138 | <p>Deutsch:<br/> | Unknown directive |
| 139 | http://de.wikipedia.org/wiki/Review_(Softwareentwicklung)<br/> | Unknown directive |
| 140 | <a href="https://de.wikipedia.org/wiki/Peer-Review">http://de.wikipedia.org/wiki/Peer-Review</a></p> | Unknown directive |
| 141 | <p>English:<br/> | Unknown directive |
| 142 | <a href="https://en.wikipedia.org/wiki/Software_review" target="_blank">http://en.wikipedia.org/wiki/Software_review</a></p> | Unknown directive |
| 143 | <p> <a href="https://en.wikipedia.org/wiki/Software_inspection" target="_blank">http://en.wikipedia.org/wiki/Software_inspection</a><br/> | Unknown directive |
| 144 | <a href="https://en.wikipedia.org/wiki/Software_peer_review" target="_blank">http://en.wikipedia.org/wiki/Software_peer_review</a><br/> | Unknown directive |
| 145 | <a href="https://en.wikipedia.org/wiki/Peer_review" target="_blank">http://en.wikipedia.org/wiki/Peer_review</a></p> | Unknown directive |
| 146 | <p>Русский:<br/> | Unknown directive |
| 147 | <a href="https://ru.wikipedia.org/wiki/%D0%A0%D0%B5%D1%86%D0%B5%D0%BD%D0%B7%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5" target="_blank">http://ru.wikipedia.org/wiki/Рецензирование</a></p> | Unknown directive |
| 148 | </div> | Syntax not understood |
| 149 | <ul class="links inline"><li class="node_translation_en first"><a href="en/home" title="Home" class="translation-link">English</a></li> | Syntax not understood |
| 150 | <li class="node_translation_ru last"><a href="ru/главная" title="Главная" class="translation-link">Русский</a></li> | Syntax not understood |
| 151 | </ul> | Syntax not understood |
| 152 | </div></div> <!-- /node-inner, /node --> | Syntax not understood |
| 153 | </div> | Syntax not understood |
| 154 | </div></div> <!-- /#content-inner, /#content --> | Syntax not understood |
| 155 | <div id="navbar"><div id="navbar-inner" class="clear-block region region-navbar"> | Syntax not understood |
| 156 | <a name="navigation" id="navigation"></a> | Syntax not understood |
| 157 | <div id="primary"> | Syntax not understood |
| 158 | <ul class="links"><li class="menu-159 active-trail first active"><a href="startseite" title="Startseite" class="active">Startseite</a></li> | Syntax not understood |
| 159 | <li class="menu-191"><a href="features" title="Features">Features</a></li> | Syntax not understood |
| 160 | <li class="menu-188"><a href="download" title="Download">Download</a></li> | Syntax not understood |
| 161 | <li class="menu-180"><a href="impressum" title="Impressum">Impressum</a></li> | Syntax not understood |
| 162 | <li class="menu-123"><a href="kontakt" title="">Kontakt</a></li> | Syntax not understood |
| 163 | <li class="menu-194 last"><a href="video" title="Video Tutorial">Video Tutorial</a></li> | Syntax not understood |
| 164 | </ul> </div> <!-- /#primary --> | Syntax not understood |
| 165 | <div id="secondary"> | Syntax not understood |
| 166 | <ul class="links"><li class="menu-196 first"><a href="blog" title="">News</a></li> | Syntax not understood |
| 167 | <li class="menu-197 last"><a href="systemanforderungen" title="Systemanforderungen">Systemanforderungen</a></li> | Syntax not understood |
| 168 | </ul> </div> <!-- /#secondary --> | Syntax not understood |
| 169 | </div></div> <!-- /#navbar-inner, /#navbar --> | Syntax not understood |
| 170 | <div id="sidebar-right"><div id="sidebar-right-inner" class="region region-right"> | Syntax not understood |
| 171 | <div id="block-locale-0" class="block block-locale region-odd odd region-count-1 count-1"><div class="block-inner"> | Syntax not understood |
| 172 | <h2 class="title">Sprachen</h2> | Syntax not understood |
| 173 | <div class="content"> | Syntax not understood |
| 174 | <ul><li class="de first active"><a href="/" class="language-link active">Deutsch</a></li> | Syntax not understood |
| 175 | <li class="en"><a href="en" class="language-link">English</a></li> | Syntax not understood |
| 176 | <li class="ru last"><a href="ru" class="language-link">Русский</a></li> | Syntax not understood |
| 177 | </ul> </div> | Syntax not understood |
| 178 | </div></div> <!-- /block-inner, /block --> | Syntax not understood |
| 179 | <div id="block-menu-secondary-links" class="block block-menu region-even even region-count-2 count-2"><div class="block-inner"> | Syntax not understood |
| 180 | <h2 class="title">Sekundärlinks</h2> | Syntax not understood |
| 181 | <div class="content"> | Syntax not understood |
| 182 | <ul class="menu"><li class="leaf first"><a href="blog" title="">News</a></li> | Syntax not understood |
| 183 | <li class="leaf last"><a href="systemanforderungen" title="Systemanforderungen">Systemanforderungen</a></li> | Syntax not understood |
| 184 | </ul> </div> | Syntax not understood |
| 185 | </div></div> <!-- /block-inner, /block --> | Syntax not understood |
| 186 | <div id="block-user-0" class="block block-user region-odd odd region-count-3 count-3"><div class="block-inner"> | Syntax not understood |
| 187 | <h2 class="title">Benutzeranmeldung</h2> | Syntax not understood |
| 188 | <div class="content"> | Syntax not understood |
| 189 | <form action="/" accept-charset="UTF-8" method="post" id="user-login-form"> | Syntax not understood |
| 190 | <div><div class="form-item" id="edit-name-wrapper"> | Syntax not understood |
| 191 | <label for="edit-name">Benutzername: <span class="form-required" title="Dieses Feld wird benötigt.">*</span></label> | Unknown directive |
| 192 | <input type="text" maxlength="60" name="name" id="edit-name" size="15" value="" class="form-text required"/> | Syntax not understood |
| 193 | </div> | Syntax not understood |
| 194 | <div class="form-item" id="edit-pass-wrapper"> | Syntax not understood |
| 195 | <label for="edit-pass">Passwort: <span class="form-required" title="Dieses Feld wird benötigt.">*</span></label> | Unknown directive |
| 196 | <input type="password" name="pass" id="edit-pass" maxlength="60" size="15" class="form-text required"/> | Syntax not understood |
| 197 | </div> | Syntax not understood |
| 198 | <input type="submit" name="op" id="edit-submit" value="Anmelden" class="form-submit"/> | Syntax not understood |
| 199 | <div class="item-list"><ul><li class="first"><a href="user/register" title="Ein neues Benutzerkonto erstellen.">Registrieren</a></li> | Syntax not understood |
| 200 | <li class="last"><a href="user/password" title="Ein neues Passwort per E-Mail anfordern.">Neues Passwort anfordern</a></li> | Syntax not understood |
| 201 | </ul></div><input type="hidden" name="form_build_id" id="form-b39d0d6367b2ba448f392ca97f9c583c" value="form-b39d0d6367b2ba448f392ca97f9c583c"/> | Syntax not understood |
| 202 | <input type="hidden" name="form_id" id="edit-user-login-block" value="user_login_block"/> | Syntax not understood |
| 203 | </div></form> | Syntax not understood |
| 204 | </div> | Syntax not understood |
| 205 | </div></div> <!-- /block-inner, /block --> | Syntax not understood |
| 206 | </div></div> <!-- /#sidebar-right-inner, /#sidebar-right --> | Syntax not understood |
| 207 | </div></div> <!-- /#main-inner, /#main --> | Syntax not understood |
| 208 | <div id="footer"><div id="footer-inner" class="region region-footer"> | Syntax not understood |
| 209 | <i style="color:#999999;display:block;padding-bottom:20px;">Copyright © 2015 PearReview -- All rights reserved.</i> | Unknown directive |
| 210 | <div id="block-menu-primary-links" class="block block-menu region-odd even region-count-1 count-4"><div class="block-inner"> | Syntax not understood |
| 211 | <h2 class="title">Hauptlinks</h2> | Syntax not understood |
| 212 | <div class="content"> | Syntax not understood |
| 213 | <ul class="menu"><li class="leaf first active-trail"><a href="startseite" title="Startseite" class="active">Startseite</a></li> | Syntax not understood |
| 214 | <li class="leaf"><a href="features" title="Features">Features</a></li> | Syntax not understood |
| 215 | <li class="leaf"><a href="download" title="Download">Download</a></li> | Syntax not understood |
| 216 | <li class="leaf"><a href="impressum" title="Impressum">Impressum</a></li> | Syntax not understood |
| 217 | <li class="leaf"><a href="kontakt" title="">Kontakt</a></li> | Syntax not understood |
| 218 | <li class="leaf last"><a href="video" title="Video Tutorial">Video Tutorial</a></li> | Syntax not understood |
| 219 | </ul> </div> | Syntax not understood |
| 220 | </div></div> <!-- /block-inner, /block --> | Syntax not understood |
| 221 | </div></div> <!-- /#footer-inner, /#footer --> | Syntax not understood |
| 222 | </div></div> <!-- /#page-inner, /#page --> | Syntax not understood |
| 223 | <script type="text/javascript"> | Syntax not understood |
| 224 | try { | Syntax not understood |
| 225 | } catch(err) {}</script> | Syntax not understood |
| 226 | <script type="module" src="https://static.cloudflareinsights.com/beacon.min.js/v4513226cdae34746b4dedf0b4dfa099e1781791509496" integrity="sha512-ZE9pZaUXND66v380QUtch/5sE9tPFh2zg45pR2PB0CVkCtOREv2AJKkSidISWkysEuQ0EH8faUU5du78bx87UQ==" data-cf-beacon='{"version":"2024.11.0","token":"333bb10ee9a14d30af4ba35090df79c8","r":1}' crossorigin="anonymous"></script> | Unknown directive |
| 227 | </body> | Syntax not understood |
| 228 | </html> | Syntax not understood |
To appear in search results, crawlers need access to your app.
○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●Document has a valid `hreflang`
○Image elements have `[alt]` attributes
○Document has a valid `rel=canonical`