9.1 sec in total
55 ms
8.7 sec
365 ms
Click here to check amazing Poetic Cases content for United States. Otherwise, check out these important facts you probably never knew about poeticcases.com
Poetic specializes in designing premium, protective, and reliable cell phone and tablet cases that offer functionality and style at an affordable price.
Visit poeticcases.comWe analyzed Poeticcases.com page load time and found that the first response time was 55 ms and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
poeticcases.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value14.0 s
0/100
25%
Value7.9 s
23/100
10%
Value2,080 ms
7/100
30%
Value0.52
15/100
15%
Value16.0 s
6/100
10%
55 ms
6886 ms
40 ms
56 ms
33 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 45% of them (45 requests) were addressed to the original Poeticcases.com, 12% (12 requests) were made to Poeticsite-extima.netdna-ssl.com and 6% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (6.9 sec) belongs to the original domain Poeticcases.com.
Page size can be reduced by 863.2 kB (49%)
1.8 MB
910.3 kB
In fact, the total size of Poeticcases.com main page is 1.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Javascripts take 906.8 kB which makes up the majority of the site volume.
Potential reduce by 51.8 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 15.3 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 51.8 kB or 82% of the original size.
Potential reduce by 41.4 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Poetic Cases images are well optimized though.
Potential reduce by 598.1 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 598.1 kB or 66% of the original size.
Potential reduce by 171.8 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Poeticcases.com needs all CSS files to be minified and compressed as it can save up to 171.8 kB or 84% of the original size.
Number of requests can be reduced by 60 (70%)
86
26
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Poetic Cases. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
poeticcases.com
55 ms
www.poeticcases.com
6886 ms
w.js
40 ms
styles.css
56 ms
jquery-ui-1.10.0.custom.min.css
33 ms
nivo-slider.css
27 ms
nivo.css
30 ms
common.css
28 ms
ajaxCart.css
40 ms
Ribbons.common.css
35 ms
Ribbons.css
34 ms
JCarousel.css
35 ms
MegaMenu.css
37 ms
InstantSearch.css
36 ms
jquery-1.7.1.min.js
68 ms
jquery.unobtrusive-ajax.min.js
36 ms
jquery.validate.min.js
63 ms
jquery.validate.unobtrusive.min.js
62 ms
jquery-ui-1.10.0.min.js
94 ms
public.common.js
61 ms
public.ajaxcart.js
60 ms
kendo.public.min.js
90 ms
jquery.touchSwipe.min.js
59 ms
AjaxCart.min.js
80 ms
jquery.json-2.2.min.js
81 ms
SevenSpikesExtensions.js
80 ms
jquery.nivo.slider.js
83 ms
jquery.json-2.4.min.js
80 ms
ProductRibbons.min.js
80 ms
jquery.jcarousel.min.js
81 ms
jquery.disable.text.select.js
81 ms
jquery.lazyload.min.js
80 ms
css
80 ms
css
143 ms
css
143 ms
clickstream.min.js
119 ms
gtmp_compiled.js
51 ms
poeticLogo.png
33 ms
0014079.jpeg
48 ms
poetic-cases-462767.js
38 ms
0010190.jpeg
24 ms
0014023_affinity_150.jpeg
21 ms
0014080_affinity_150.jpeg
22 ms
0013742_duo_150.jpeg
23 ms
0013869_loft_150.jpeg
34 ms
0014464_quarterback-whitedark-red_150.jpeg
32 ms
0013477_revolution_150.jpeg
35 ms
0013905_slimline_150.jpeg
31 ms
0013781_turtle-skin_150.jpeg
34 ms
0013251_view_150.jpeg
36 ms
0013758_volante_150.jpeg
36 ms
ico-cart.png
42 ms
search_icon.png
43 ms
homeslidebg.png
41 ms
review-program-banner.jpg
57 ms
blogLogo.png
40 ms
icon-fb.png
40 ms
icon-twitter.png
53 ms
instagram.png
50 ms
viewmobile.png
52 ms
poeticLogo.png
50 ms
i.js
41 ms
ed104ed326e02f1e48152e19866123d5a08a2b96.1.js
45 ms
7c5a5d9f-1e04-4eda-a6be-11b9de3a74fe.js
56 ms
gtmp_compiled_FD-w6i_oWUw.js
57 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
33 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
64 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
66 ms
WRf4.js
21 ms
Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf
31 ms
b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf
124 ms
b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf
122 ms
dc.js
74 ms
loader.gif
62 ms
storage.luckyorange.net
66 ms
prev-horizontal.png
33 ms
next-horizontal.png
37 ms
__utm.gif
11 ms
2-poetic-cases-462767.css
30 ms
roundtrip.js
10 ms
settings.luckyorange.net
53 ms
YRP2Y5LFWRBXLKYTWP37EX.js
158 ms
24 ms
mutation.min.js
32 ms
reset.css
10 ms
out
14 ms
tr
66 ms
30 ms
out
50 ms
out
51 ms
out
50 ms
54 ms
u.php
43 ms
pixel
78 ms
sd
16 ms
Pug
1016 ms
377928.gif
8 ms
in
6 ms
tap.php
188 ms
e
5 ms
poeticcases.com accessibility score
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.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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.
Impact
Issue
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
poeticcases.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
poeticcases.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Poeticcases.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Poeticcases.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
poeticcases.com
Open Graph description is not detected on the main page of Poetic Cases. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: