14.3 sec in total
2.5 sec
11.3 sec
534 ms
Click here to check amazing Dear Phones content. Otherwise, check out these important facts you probably never knew about dearphones.com
Blog dedicado a todo lo que necesitas saber sobre el extenso mundo de los smartphones, tablets y wearables. Encontrarás novedades, rumores, opiniones...
Visit dearphones.comWe analyzed Dearphones.com page load time and found that the first response time was 2.5 sec and then it took 11.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
dearphones.com performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value19.2 s
0/100
25%
Value35.2 s
0/100
10%
Value70,480 ms
0/100
30%
Value0.002
100/100
15%
Value99.6 s
0/100
10%
2532 ms
158 ms
371 ms
395 ms
417 ms
Our browser made a total of 128 requests to load all elements on the main page. We found that 29% of them (37 requests) were addressed to the original Dearphones.com, 16% (20 requests) were made to I0.wp.com and 11% (14 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4 sec) relates to the external source I0.wp.com.
Page size can be reduced by 280.5 kB (14%)
2.0 MB
1.7 MB
In fact, the total size of Dearphones.com main page is 2.0 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 168.7 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 22.8 kB, which is 11% 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 168.7 kB or 84% of the original size.
Potential reduce by 42 B
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. Dear Phones images are well optimized though.
Potential reduce by 26.8 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 26.8 kB or 15% of the original size.
Potential reduce by 84.9 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. Dearphones.com needs all CSS files to be minified and compressed as it can save up to 84.9 kB or 30% of the original size.
Number of requests can be reduced by 74 (67%)
110
36
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dear Phones. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
dearphones.com
2532 ms
wp-emoji-release.min.js
158 ms
style.min.css
371 ms
mediaelementplayer-legacy.min.css
395 ms
wp-mediaelement.min.css
417 ms
styles.css
420 ms
css
133 ms
main.css
867 ms
font-awesome.4.7.0.swap.min.css
424 ms
penci-icon.css
460 ms
style.css
476 ms
social-counter.css
505 ms
elementor-icons.min.css
506 ms
frontend-legacy.min.css
511 ms
frontend.min.css
602 ms
post-7409.css
575 ms
global.css
628 ms
customizer-style.min.css
630 ms
gdpr-main-nf.css
650 ms
css
102 ms
jetpack.css
725 ms
jquery.min.js
784 ms
jquery-migrate.min.js
711 ms
adsbygoogle.js
238 ms
adsbygoogle.js
262 ms
photon.min.js
723 ms
index.js
758 ms
index.js
805 ms
iframe_api
255 ms
play.js
1341 ms
penci-lazy.js
1342 ms
libs-script.min.js
1364 ms
main.js
1360 ms
post-like.js
1358 ms
api.js
285 ms
regenerator-runtime.min.js
1358 ms
wp-polyfill.min.js
1360 ms
index.js
1350 ms
main.js
1351 ms
OneSignalSDK.js
229 ms
e-202239.js
211 ms
Widget_2.js
144 ms
logo-dp.png
997 ms
logo-dp.png
197 ms
fontawesome-webfont.woff
408 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0Uz.woff
132 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0Uz.woff
228 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFV0Uz.woff
227 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FV0Uz.woff
225 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-h4-FV0Uz.woff
334 ms
penciicon.ttf
216 ms
sdk.js
206 ms
sdk.js
37 ms
289 ms
show_ads_impl.js
81 ms
zrt_lookup.html
309 ms
cookie.js
122 ms
integrator.js
162 ms
ads
522 ms
ads
724 ms
ads
1195 ms
css
91 ms
cup-border.png
134 ms
integrator.js
121 ms
ads
579 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkBgv58a-xA.woff
25 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xA.woff
26 ms
integrator.js
24 ms
ads
432 ms
reactive_library.js
51 ms
www-widgetapi.js
25 ms
iPhone-14.png
1429 ms
samsung-galaxy-z-fold4-y-z-flip4.png
1712 ms
Xiaomi-12S-Ultra.jpg
1421 ms
Sony-Xperia-IV.jpg
1421 ms
Samsung-Galaxy-Tab-S8.jpg
1423 ms
Samsung-Galaxy-S22.jpg
1420 ms
Xiaomi-12-portada.jpg
2267 ms
Huawei-P50-Pocket.jpg
2326 ms
SAMSUNG-GALAXY-S23-render_1.png
2411 ms
Vivo-X-Fold-Plus.png
2393 ms
Isla-dinamica-Android.jpg
2212 ms
Xiaomi-12T.png
2763 ms
Honor-X40-5G.png
3948 ms
OnePlus-11-Pro-1.png
3252 ms
iPhone-X_2.png
2583 ms
emergencia.png
3886 ms
Oppo-SuperVOOC-240W.jpg
3270 ms
RED_Hydrogen.png
3901 ms
emergencia.png
3967 ms
integrator.js
103 ms
zrt_lookup.html
79 ms
recaptcha__en.js
320 ms
css2
79 ms
downsize_200k_v1
647 ms
load_preloaded_resource.js
737 ms
abg_lite.js
734 ms
window_focus.js
734 ms
qs_click_protection.js
750 ms
rx_lidar.js
677 ms
042791247ab671b2831aa311d6583330.js
551 ms
interstitial_ad_frame.js
887 ms
icon.png
227 ms
feedback_grey600_24dp.png
263 ms
settings_grey600_24dp.png
263 ms
css
484 ms
m_js_controller.js
820 ms
73529d2ef9ae0d2e533acdf960ac9616.js
123 ms
85254efcadaacab5fed344cbf203b7e7.js
129 ms
5bc871197ab2c7870c35674d08f1b35e.js
127 ms
c471d9b7113df21a6cf58632ab968748.js
127 ms
KFOlCnqEu92Fr1MmWUlvAA.woff
249 ms
KFOmCnqEu92Fr1Me5g.woff
400 ms
s
513 ms
downsize_200k_v1
410 ms
css
333 ms
312 ms
css
176 ms
KFOmCnqEu92Fr1Mu4mxM.woff
151 ms
activeview
39 ms
b4aq_x9zMiku-4ayY0gQrcEuJNMSghrM2Nuaea2nyAg.js
33 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
29 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
28 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpy8.woff
129 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpy8.woff
128 ms
activeview
140 ms
admin-ajax.php
2139 ms
js
56 ms
dearphones.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
dearphones.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
dearphones.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dearphones.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Dearphones.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.
dearphones.com
Open Graph data is detected on the main page of Dear Phones. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: