Dolphy.school Site Title

ONLINE Insurance Courses. Cursos de Seguros en Linea. Dolphy™ School

Dolphy.school Meta Description

Nuevos Cursos

Dolphy.school Test Results

Dolphy.school Mobile Performance: 14/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Remove unused JavaScript. Potential savings of 1,038 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Preload key requests. Potential savings of 6,420 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.
Serve images in next-gen formats. Potential savings of 524 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Defer offscreen images. Potential savings of 643 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Remove unused CSS. Potential savings of 172 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Efficiently encode images. Potential savings of 151 KiB
Optimized images load faster and consume less cellular data. Learn more.
Eliminate render-blocking resources. Potential savings of 1,660 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Minify JavaScript. Potential savings of 4 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
Properly size images. Potential savings of 23 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
Reduce the impact of third-party code
Third-party code blocked the main thread for 2,900 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
Minimize main-thread work
13.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce JavaScript execution time
9.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Serve static assets with an efficient cache policy
51 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoid enormous network payloads
Total size was 3,327 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Avoid an excessive DOM size
1,102 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
User Timing marks and measures
8 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
Avoid long main-thread tasks
20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid chaining critical requests
11 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Keep request counts low and transfer sizes small
98 requests • 3,327 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid large layout shifts
2 elements found
These DOM elements contribute most to the CLS of the page.

Dolphy.school Mobile SEO: 91/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 more.
Tap targets are not sized appropriately
97% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
548 errors found
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.

Dolphy.school 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
Missing source maps for large first-party JavaScript
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.
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 more.
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 servedover 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.
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
Includes front-end JavaScript libraries with known security vulnerabilities
2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Dolphy.school Mobile Progressive Web App: 21/100
Quick overview:
Fast and reliable
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Page load is not fast enough on mobile networks
Interactive at 23.9 s
A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
PWA Optimized
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
Installable
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 servedover 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.
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Dolphy.school Mobile Accessibility: 0/100
Quick overview:
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.
ARIA input fields do not have accessible names
When an input field 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 more.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.
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.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
Links do not have a discernible name
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 more.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn more.
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.
Some elements have a `[tabindex]` value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more.
Similar tests
www.dolphy.com
www.dolphy.net
www.dolphy.org
www.dolphy.info
www.dolphy.biz
www.dolphy.us
www.dolphy.mobi
www.olphy.school
www.dolphy.school
www.xolphy.school
www.dxolphy.school
www.xdolphy.school
www.solphy.school
www.dsolphy.school
www.sdolphy.school
www.eolphy.school
www.deolphy.school
www.edolphy.school
www.rolphy.school
www.drolphy.school
www.rdolphy.school
www.folphy.school
www.dfolphy.school
www.fdolphy.school
www.colphy.school
www.dcolphy.school
www.cdolphy.school
www.dlphy.school
www.dilphy.school
www.doilphy.school
www.diolphy.school
www.dklphy.school
www.doklphy.school
www.dkolphy.school
www.dllphy.school
www.dollphy.school
www.dlolphy.school
www.dplphy.school
www.doplphy.school
www.dpolphy.school
www.dophy.school
www.dopphy.school
www.dolpphy.school
www.doophy.school
www.dolophy.school
www.doolphy.school
www.dokphy.school
www.dolkphy.school
www.dolhy.school
www.dolohy.school
www.dolpohy.school
www.dollhy.school
www.dolplhy.school
www.dolpy.school
www.dolpby.school
www.dolphby.school
www.dolpbhy.school
www.dolpgy.school
www.dolphgy.school
www.dolpghy.school
www.dolpyy.school
www.dolphyy.school
www.dolpyhy.school
www.dolpuy.school
www.dolphuy.school
www.dolpuhy.school
www.dolpjy.school
www.dolphjy.school
www.dolpjhy.school
www.dolpny.school
www.dolphny.school
www.dolpnhy.school
www.dolph.school
www.dolpht.school
www.dolphyt.school
www.dolphty.school
www.dolphg.school
www.dolphyg.school
www.dolphh.school
www.dolphyh.school
www.dolphhy.school
www.dolphu.school
www.dolphyu.school
Last Tested: