Forogore.net Test Results

Forogore.net Mobile Performance: 48/100
Quick overview:
Time to Interactive
12.4 s
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.
Max Potential First Input Delay
380 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.
First Meaningful Paint
2.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Metrics
Collects all available metrics.
Network Round Trip Times
170 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.
Server Backend Latencies
350 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
Final Screenshot
The last screenshot captured of the pageload.

423575922952

Script Treemap Data
Used for treemap app
Network Requests
Lists the network requests that were made during page load.
Diagnostics
Collection of useful page vitals.
Tasks
Lists the toplevel main thread tasks that executed during page load.

Forogore.net Mobile SEO: 97/100
Quick overview:
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn how to make pages mobile-friendly.
Tap targets are not sized appropriately
71% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.

Forogore.net Mobile Best Practices: 64/100
Quick overview:
General
Browser errors were logged to the console
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
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Trust and Safety
Does not use HTTPS
1 insecure request found
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.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Forogore.net Mobile PWA: 88/100
Quick overview:
PWA Optimized
Content is not sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn how to size content for the viewport. The viewport size of 738px does not match the window size of 412px.
Forogore.net Mobile Accessibility: 83/100
Quick overview:
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
Names and labels
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.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`button`, `link`, and `menuitem` elements do not have accessible names.
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
Document has a main landmark.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Touch targets have sufficient size and spacing.
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.
Identical links have the same purpose.
Links with the same destination should have the same description, to help users understand the link's purpose and decide whether to follow it. Learn more about identical links.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
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.
Similar tests
www.forogore.com
www.forogore.net
www.forogore.org
www.forogore.info
www.forogore.biz
www.forogore.us
www.forogore.mobi
www.orogore.net
www.forogore.net
www.corogore.net
www.fcorogore.net
www.cforogore.net
www.dorogore.net
www.fdorogore.net
www.dforogore.net
www.rorogore.net
www.frorogore.net
www.rforogore.net
www.torogore.net
www.ftorogore.net
www.tforogore.net
www.gorogore.net
www.fgorogore.net
www.gforogore.net
www.vorogore.net
www.fvorogore.net
www.vforogore.net
www.frogore.net
www.firogore.net
www.foirogore.net
www.fiorogore.net
www.fkrogore.net
www.fokrogore.net
www.fkorogore.net
www.flrogore.net
www.folrogore.net
www.florogore.net
www.fprogore.net
www.foprogore.net
www.fporogore.net
www.foogore.net
www.foeogore.net
www.foreogore.net
www.foerogore.net
www.fodogore.net
www.fordogore.net
www.fodrogore.net
www.fofogore.net
www.forfogore.net
www.fofrogore.net
www.fotogore.net
www.fortogore.net
www.fotrogore.net
www.forgore.net
www.forigore.net
www.foroigore.net
www.foriogore.net
www.forkgore.net
www.forokgore.net
www.forkogore.net
www.forlgore.net
www.forolgore.net
www.forlogore.net
www.forpgore.net
www.foropgore.net
www.forpogore.net
www.foroore.net
www.forofore.net
www.forogfore.net
www.forofgore.net
www.forovore.net
www.forogvore.net
www.forovgore.net
www.forotore.net
www.forogtore.net
www.forotgore.net
www.forobore.net
www.forogbore.net
www.forobgore.net
www.foroyore.net
www.forogyore.net
www.foroygore.net
www.forohore.net
www.foroghore.net
www.forohgore.net
www.forogre.net
www.forogire.net
www.forogoire.net
www.forogiore.net
www.forogkre.net
www.forogokre.net
www.forogkore.net
www.foroglre.net
www.forogolre.net
www.foroglore.net
www.forogpre.net
www.forogopre.net
www.forogpore.net
www.forogoe.net
www.forogoee.net
www.forogoree.net
www.forogoere.net
www.forogode.net
www.forogorde.net
www.forogodre.net
www.forogofe.net
www.forogorfe.net
www.forogofre.net
www.forogote.net
www.forogorte.net
www.forogotre.net
www.forogor.net
www.forogorw.net
www.forogorew.net
www.forogorwe.net
www.forogors.net
www.forogores.net
www.forogorse.net
www.forogord.net
www.forogored.net
www.forogorr.net
www.forogorer.net
www.forogorre.net
Last Tested: