Drwn.ru Site Title

Рекламные и корпоративные сувениры с нанесением логотипа: изготовление сувенирной продукции на заказ

Drwn.ru Meta Description

Более 15 лет опыта. Минимальный заказ оптом от 15000 руб. Нанесение корпоративных логотипов для сувенирной продукции. Доставка по Москве, Спб и по РФ.

Drwn.ru Test Results

Drwn.ru Mobile Performance: 28/100
Quick overview:
Time to Interactive
21.5 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
680 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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Minify JavaScript
Potential savings of 192 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Minimize main-thread work
19.1 s
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
Reduce unused JavaScript
Potential savings of 1,331 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.
Eliminate render-blocking resources
Potential savings of 5,080 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Reduce unused CSS
Potential savings of 98 KiB
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.
Reduce the impact of third-party code
Third-party code blocked the main thread for 6,250 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 how to minimize third-party impact.
Minify CSS
Potential savings of 15 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Avoid multiple page redirects
Potential savings of 1,250 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Avoid an excessive DOM size
1,503 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Reduce JavaScript execution time
13.3 s
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.
Largest Contentful Paint element
11,710 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Avoid enormous network payloads
Total size was 4,869 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Defer offscreen images
Potential savings of 98 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Serve static assets with an efficient cache policy
135 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
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 about `font-display`.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 6 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
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 about adopting passive event listeners.

Drwn.ru Mobile SEO: 92/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
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

Drwn.ru Mobile Best Practices: 76/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
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.
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration. Document must contain a doctype
Drwn.ru Mobile Accessibility: 60/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 toggle fields do not have accessible names
When a toggle 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 about toggle fields.
`[aria-*]` attributes do not match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.
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 about input field labels.
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 about roles and required children elements.
`[aria-*]` attributes do not have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
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.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
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.
Touch targets do not have sufficient size or 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.
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.
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 how to make links accessible.
Image elements have `[alt]` attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the `alt` attribute.
Input buttons do not have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
Similar tests
www.drwn.com
www.drwn.net
www.drwn.org
www.drwn.info
www.drwn.biz
www.drwn.us
www.drwn.mobi
www.rwn.ru
www.drwn.ru
www.xrwn.ru
www.dxrwn.ru
www.xdrwn.ru
www.srwn.ru
www.dsrwn.ru
www.sdrwn.ru
www.erwn.ru
www.derwn.ru
www.edrwn.ru
www.rrwn.ru
www.drrwn.ru
www.rdrwn.ru
www.frwn.ru
www.dfrwn.ru
www.fdrwn.ru
www.crwn.ru
www.dcrwn.ru
www.cdrwn.ru
www.dwn.ru
www.dewn.ru
www.drewn.ru
www.ddwn.ru
www.drdwn.ru
www.ddrwn.ru
www.dfwn.ru
www.drfwn.ru
www.dtwn.ru
www.drtwn.ru
www.dtrwn.ru
www.drn.ru
www.drqn.ru
www.drwqn.ru
www.drqwn.ru
www.dran.ru
www.drwan.ru
www.drawn.ru
www.drsn.ru
www.drwsn.ru
www.drswn.ru
www.dren.ru
www.drwen.ru
www.drw.ru
www.drwb.ru
www.drwnb.ru
www.drwbn.ru
www.drwh.ru
www.drwnh.ru
www.drwhn.ru
www.drwj.ru
www.drwnj.ru
www.drwjn.ru
www.drwm.ru
www.drwnm.ru
www.drwmn.ru
Last Tested: