Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

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.

Request	Cache TTL	Transfer Size
iosoccer.com/assets/images/iosoccer/screenshots/2_compressed.jpg	0.0 ms	871.9 KiB
iosoccer.com/main-es2015.1f612830ca4823c9ab64.js	0.0 ms	652.8 KiB
iosoccer.com/assets/images/iosoccer/screenshots/1_compressed.jpg	0.0 ms	598.3 KiB
iosoccer.com/assets/images/iosoccer/screenshots/10_compressed.jpg	0.0 ms	523.1 KiB
iosoccer.com/assets/images/iosoccer/screenshots/5_compressed.jpg	0.0 ms	475.9 KiB
iosoccer.com/assets/images/iosoccer/screenshots/4_compressed.jpg	0.0 ms	408.0 KiB
iosoccer.com/assets/images/iosoccer/screenshots/3_compressed.jpg	0.0 ms	349.2 KiB
iosoccer.com/assets/images/iosoccer/screenshots/9_compressed.jpg	0.0 ms	276.6 KiB
iosoccer.com/assets/images/iosoccer/screenshots/8_compressed.jpg	0.0 ms	217.9 KiB
iosoccer.com/assets/images/iosoccer/screenshots/6_compressed.jpg	0.0 ms	214.7 KiB
iosoccer.com/assets/images/iosoccer/screenshots/7_compressed.jpg	0.0 ms	161.4 KiB
store.fastly.steamstatic.com/public/shared/fonts/MotivaSans-Light.ttf?v=4.015	0.0 ms	120.1 KiB
store.fastly.steamstatic.com/public/shared/fonts/MotivaSans-Regular.ttf?v=4.015	0.0 ms	120.0 KiB
iosoccer.com/styles.72a1283fe5aa0bb5da26.css	0.0 ms	117.5 KiB
iosoccer.com/es.36cdd00d34fa3ab9d98a.svg	0.0 ms	90.0 KiB
iosoccer.com/assets/fonts/font-awesome/webfonts/fa-brands-400.woff2	0.0 ms	73.8 KiB
iosoccer.com/assets/images/logos/iosoccer-full-logo-medium.png	0.0 ms	16.8 KiB
iosoccer.com/polyfills-es2015.e39d57420bbc09ea6a24.js	0.0 ms	12.2 KiB
iosoccer.com/assets/fonts/font-awesome/css/all.min.css	0.0 ms	11.7 KiB
www.statcounter.com/counter/counter.js	43200.0 s	17.5 KiB
iosoccer.com/pt.96475126e7232ee3558e.svg	0.0 ms	8.3 KiB
iosoccer.com/assets/images/logos/simrai.png	0.0 ms	7.9 KiB
iosoccer.com/assets/images/logos/iosoccer-full-logo-small.png	0.0 ms	7.5 KiB
iosoccer.com/assets/fonts/font-awesome/css/v4-shims.min.css	0.0 ms	4.0 KiB
iosoccer.com/assets/fonts/simple-line-icons/css/simple-line-icons.css	0.0 ms	2.6 KiB
iosoccer.com/kr.6bd5eda73cbc171baedb.svg	0.0 ms	1.9 KiB
iosoccer.com/runtime-es2015.c3d4fbaa550ce2d063a8.js	0.0 ms	1.2 KiB
iosoccer.com/gb.516897fd3988e35032b7.svg	0.0 ms	708 B
cdn.fastly.steamstatic.com/store/icons/icon_platform_win.svg	0.0 ms	641 B
iosoccer.com/ru.7e04b988972d41f5c369.svg	0.0 ms	456 B
static.doubleclick.net/instream/ad_status.js	900.0 s	495 B
iosoccer.com/cz.5a24757d105fbe7a4e81.svg	0.0 ms	397 B
iosoccer.com/pl.2b5541c54505328dbc1b.svg	0.0 ms	391 B

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.

URL	Est Savings
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	85 ms
iosoccer.com/assets/fonts/font-awesome/webfonts/fa-brands-400.woff2	70 ms
fonts.gstatic.com/s/montserrat/v31/JTUSjIg1_i6t8kCHKm459WlhyyTh89Y.woff2	55 ms
/s/sourcesanspro/v23/6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj...	40 ms
store.fastly.steamstatic.com/public/shared/fonts/MotivaSans-Light.ttf?v=4.015	15 ms
store.fastly.steamstatic.com/public/shared/fonts/MotivaSans-Regular.ttf?v=4.015	10 ms

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:41.597 source:map[type:text value:[unattributed]]]]

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: div.site-wrapper > div#page-content > app-hero > div.ios-hero__item

path: 1,HTML,1,BODY,0,APP-ROOT,0,DIV,3,DIV,1,APP-HERO,0,DIV

selector: div.site-wrapper > div#page-content > app-hero > div.ios-hero__item

snippet: <div _ngcontent-plq-c18="" class="ios-hero__item" style="background-image: url("./assets/images/iosoccer/screenshots/1_compressed.j…");">

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

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.

URL	Transfer Size	Duration
/css?family=Montserrat:300,400,500,600,700%7CSource+Sans+...	1.4 KiB	328 ms
iosoccer.com/styles.72a1283fe5aa0bb5da26.css	117.5 KiB	189 ms
iosoccer.com/assets/fonts/font-awesome/css/all.min.css	11.7 KiB
iosoccer.com/assets/fonts/simple-line-icons/css/simple-line-icons.css	2.6 KiB
iosoccer.com/assets/fonts/font-awesome/css/v4-shims.min.css	4.0 KiB	63 ms

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
IOSoccer `div.header__primary-inner > div.header-logo > a > img.header-logo__img`	iosoccer.com/assets/images/logos/iosoccer-full-logo-small.png	7.3 KiB	5.6 KiB

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

Diagnostics

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 60 ms 126.1 KiB

URL	Transfer Size	Est Savings
iosoccer.com/styles.72a1283fe5aa0bb5da26.css	117.3 KiB	114.6 KiB
iosoccer.com/assets/fonts/font-awesome/css/all.min.css	11.6 KiB	11.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 380 ms 459.4 KiB

URL	Transfer Size	Est Savings
iosoccer.com/main-es2015.1f612830ca4823c9ab64.js	651.7 KiB	459.4 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
iosoccer.com/assets/images/iosoccer/screenshots/2_compressed.jpg	871.9 KiB
iosoccer.com/main-es2015.1f612830ca4823c9ab64.js	652.8 KiB
iosoccer.com/assets/images/iosoccer/screenshots/1_compressed.jpg	598.3 KiB
iosoccer.com/assets/images/iosoccer/screenshots/10_compressed.jpg	523.1 KiB
iosoccer.com/assets/images/iosoccer/screenshots/5_compressed.jpg	475.9 KiB
www.youtube.com/s/player/8fb635c2/player_embed_es6.vflset/en_US/base.js	435.9 KiB
iosoccer.com/assets/images/iosoccer/screenshots/4_compressed.jpg	408.0 KiB
iosoccer.com/assets/images/iosoccer/screenshots/3_compressed.jpg	349.2 KiB
iosoccer.com/assets/icons/favicon.ico	307.7 KiB
iosoccer.com/assets/images/iosoccer/screenshots/9_compressed.jpg	276.6 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
IOSoccer `div.header__primary-inner > div.header-logo > a > img.header-logo__img`	iosoccer.com/assets/images/logos/iosoccer-full-logo-small.png
div.footer-col-inner > div.footer-logo > a > img.footer-logo__img `div.footer-col-inner > div.footer-logo > a > img.footer-logo__img`	iosoccer.com/assets/images/logos/iosoccer-full-logo-small.png
SimRai logo `ul.sponsors-logos > li.sponsors__item > a > img`	iosoccer.com/assets/images/logos/simrai.png

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Max Potential First Input Delay 70 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 28 user timings

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.5 s

●Avoid long main-thread tasks 4 long tasks found

●Network Requests

●Network Round Trip Times 70 ms

●Server Backend Latencies 220 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 30 ms

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

○Avoid non-composited animations

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
JOIN OUR DISCORD `div.container > ul.info-block > a.btn > span`
INFO@IOSOCCER.COM `div.widget__content > div.widget-contact-info__body > div.info-block__item > a.info-block__link`
INFO@IOSOCCER.COM `div.widget__content > div.widget-contact-info__body > div.info-block__item > a.info-block__link`
SEND YOUR MESSAGE `div.widget > div.widget__content > form.contact-form > button.btn`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
IOSOCCER `div.row > div.col-md-4 > div.footer-copyright > a`

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.ios-hero__item > div.ios-hero__item--download > div > iframe.ios-hero__item--video `div.ios-hero__item > div.ios-hero__item--download > div > iframe.ios-hero__item--video`
app-hero > div.ios-hero__item > div > iframe.ios-hero__item--steam-widget `app-hero > div.ios-hero__item > div > iframe.ios-hero__item--steam-widget`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-sm-6 > div.footer-col-inner > div.footer-logo > a `div.col-sm-6 > div.footer-col-inner > div.footer-logo > a`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
OUR SPONSOR: `div.footer-widgets > div.container > div.sponsors > h6.sponsors-title`

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
INSTALL VIA STEAM JOIN OUR DISCORD `header.header > div.header__secondary > div.container > ul.info-block`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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 `html`

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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

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

100

Best Practices

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
iosoccer.com/main-es2015.1f612830ca4823c9ab64.js

●Uses HTTPS

●Avoids deprecated APIs

●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

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●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

○Redirects HTTP traffic to HTTPS

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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
LANGUAGE: `div.header__top-bar-inner > ul.nav-account > li.nav-account__item > a`
li.nav-account__item > ul.main-nav__sub > li > a `li.nav-account__item > ul.main-nav__sub > li > a`
li.nav-account__item > ul.main-nav__sub > li > a `li.nav-account__item > ul.main-nav__sub > li > a`
li.nav-account__item > ul.main-nav__sub > li > a `li.nav-account__item > ul.main-nav__sub > li > a`
li.nav-account__item > ul.main-nav__sub > li > a `li.nav-account__item > ul.main-nav__sub > li > a`
li.nav-account__item > ul.main-nav__sub > li > a `li.nav-account__item > ul.main-nav__sub > li > a`
li.nav-account__item > ul.main-nav__sub > li > a `li.nav-account__item > ul.main-nav__sub > li > a`
li.nav-account__item > ul.main-nav__sub > li > a `li.nav-account__item > ul.main-nav__sub > li > a`
REGION: EUROPE `div.header__top-bar-inner > ul.nav-account > li.nav-account__item > a`
li.nav-account__item > ul.main-nav__sub > li > a `li.nav-account__item > ul.main-nav__sub > li > a`
li.nav-account__item > ul.main-nav__sub > li > a `li.nav-account__item > ul.main-nav__sub > li > a`
li.nav-account__item > ul.main-nav__sub > li > a `li.nav-account__item > ul.main-nav__sub > li > a`
li.nav-account__item > ul.main-nav__sub > li > a `li.nav-account__item > ul.main-nav__sub > li > a`
li.nav-account__item > ul.main-nav__sub > li > a `li.nav-account__item > ul.main-nav__sub > li > a`
li.nav-account__item > ul.main-nav__sub > li > a `li.nav-account__item > ul.main-nav__sub > li > a`
SUPPORT `nav.main-nav > ul.main-nav__list > li.has-children > a`
HUB `nav.main-nav > ul.main-nav__list > li.has-children > a`
INFO `nav.main-nav > ul.main-nav__list > li.has-children > a`

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	`<!DOCTYPE html>`	`Syntax not understood`
2	`<html lang="en">`	`Syntax not understood`
4	`<head>`	`Syntax not understood`
6	`<title>IOSoccer</title>`	`Syntax not understood`
7	`<base href="/">`	`Syntax not understood`
8	`<meta charset="utf-8">`	`Syntax not understood`
9	`<meta http-equiv="X-UA-Compatible" content="IE=edge">`	`Syntax not understood`
10	`<meta name="description" content="Homepage for IOSoccer, a third person online multiplayer soccer game">`	`Syntax not understood`
11	`<meta name="author" content="IOSoccer Team">`	`Syntax not understood`
12	`<meta name="keywords" content="iosoccer soccer game online">`	`Syntax not understood`
14	`<link rel="apple-touch-icon" sizes="120x120" href="assets/icons/apple-touch-icon.png">`	`Syntax not understood`
15	`<link rel="icon" type="image/png" sizes="32x32" href="assets/icons/favicon-32x32.png">`	`Syntax not understood`
16	`<link rel="icon" type="image/png" sizes="16x16" href="assets/icons/favicon-16x16.png">`	`Syntax not understood`
17	`<link rel="manifest" href="assets/icons/site.webmanifest">`	`Syntax not understood`
18	`<link rel="mask-icon" href="assets/icons/safari-pinned-tab.svg" color="#5bbad5">`	`Syntax not understood`
19	`<link rel="shortcut icon" href="assets/icons/favicon.ico">`	`Syntax not understood`
20	`<meta name="msapplication-TileColor" content="#da532c">`	`Syntax not understood`
21	`<meta name="msapplication-config" content="assets/icons/browserconfig.xml">`	`Syntax not understood`
22	`<meta name="theme-color" content="#ffffff">`	`Syntax not understood`
24	`<meta name="viewport" content="width=device-width,initial-scale=1.0,maximum-scale=1.0,user-scalable=0">`	`Syntax not understood`
26	`<link href="https://fonts.googleapis.com/css?family=Montserrat:300,400,500,600,700%7CSource+Sans+Pro:400,700"`	`Unknown directive`
27	`rel="stylesheet">`	`Syntax not understood`
29	`<link href="assets/fonts/font-awesome/css/all.min.css" rel="stylesheet">`	`Syntax not understood`
30	`<link href="assets/fonts/font-awesome/css/v4-shims.min.css" rel="stylesheet">`	`Syntax not understood`
31	`<link href="assets/fonts/simple-line-icons/css/simple-line-icons.css" rel="stylesheet">`	`Syntax not understood`
33	`<!-- Default Statcounter code for IOSoccer https://www.iosoccer.com -->`	`Unknown directive`
34	`<script type="text/javascript">`	`Syntax not understood`
35	`var sc_project=12897828;`	`Syntax not understood`
36	`var sc_invisible=1;`	`Syntax not understood`
37	`var sc_security="0067c3ac";`	`Syntax not understood`
38	`</script>`	`Syntax not understood`
39	`<script type="text/javascript"`	`Syntax not understood`
40	`src="https://www.statcounter.com/counter/counter.js" async></script>`	`Unknown directive`
41	`<!-- End of Statcounter Code -->`	`Syntax not understood`
43	`<link rel="stylesheet" href="styles.72a1283fe5aa0bb5da26.css"></head>`	`Syntax not understood`
45	`<body>`	`Syntax not understood`
46	`<app-root>`	`Syntax not understood`
47	`<div class="preloader-container">`	`Syntax not understood`
48	`<div class="preloader light"></div>`	`Syntax not understood`
49	`</div>`	`Syntax not understood`
50	`</app-root>`	`Syntax not understood`
51	`<script src="runtime-es2015.c3d4fbaa550ce2d063a8.js" type="module"></script><script src="runtime-es5.c3d4fbaa550ce2d063a8.js" nomodule defer></script><script src="polyfills-es5.50135ddf6e318e8abaaa.js" nomodule defer></script><script src="polyfills-es2015.e39d57420bbc09ea6a24.js" type="module"></script><script src="main-es2015.1f612830ca4823c9ab64.js" type="module"></script><script src="main-es5.1f612830ca4823c9ab64.js" nomodule defer></script></body>`	`Syntax not understood`
53	`</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

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`