4.5 sec in total
167 ms
3.9 sec
429 ms
Click here to check amazing PANDR EYEZ content. Otherwise, check out these important facts you probably never knew about pandreyez.com
Visit pandreyez.comWe analyzed Pandreyez.com page load time and found that the first response time was 167 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
pandreyez.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value14.0 s
0/100
25%
Value13.3 s
2/100
10%
Value670 ms
45/100
30%
Value0
100/100
15%
Value14.8 s
8/100
10%
167 ms
337 ms
183 ms
300 ms
315 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 82% of them (73 requests) were addressed to the original Pandreyez.com, 10% (9 requests) were made to W.soundcloud.com and 3% (3 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Pandreyez.com.
Page size can be reduced by 912.7 kB (16%)
5.7 MB
4.8 MB
In fact, the total size of Pandreyez.com main page is 5.7 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 4.3 MB which makes up the majority of the site volume.
Potential reduce by 34.1 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 34.1 kB or 77% of the original size.
Potential reduce by 43.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. PANDR EYEZ images are well optimized though.
Potential reduce by 497.4 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 497.4 kB or 68% of the original size.
Potential reduce by 337.7 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. Pandreyez.com needs all CSS files to be minified and compressed as it can save up to 337.7 kB or 58% of the original size.
Number of requests can be reduced by 57 (70%)
81
24
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PANDR EYEZ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
pandreyez.com
167 ms
www.pandreyez.com
337 ms
flexslider.css
183 ms
ut.portfolio.style.css
300 ms
prettyPhoto.css
315 ms
ut-responsive-grid.css
302 ms
font-awesome.css
215 ms
ut.shortcode.css
119 ms
ut.twitter.css
192 ms
styles.css
252 ms
settings.css
277 ms
dynamic-captions.css
287 ms
static-captions.css
321 ms
ut-fontface.css
349 ms
ut-superfish.css
359 ms
style.css
371 ms
jquery.js
384 ms
jquery-migrate.min.js
406 ms
jquery.themepunch.plugins.min.js
410 ms
jquery.themepunch.revolution.min.js
424 ms
jquery.isotope.min.js
438 ms
jquery.flexslider-min.js
453 ms
jquery.queryloader2.min.js
456 ms
device.min.js
457 ms
modernizr.min.js
494 ms
jquery.form.min.js
560 ms
scripts.js
563 ms
jquery.scrollTo.min.js
560 ms
jquery.prettyPhoto.min.js
561 ms
tabs.collapse.min.js
561 ms
jquery.visible.min.js
685 ms
jquery.fitvids.js
563 ms
ut.scplugin.js
562 ms
toucheffects.min.js
710 ms
jquery.easing.min.js
694 ms
superfish.min.js
922 ms
retina.min.js
928 ms
jquery.mb.YTPlayer.min.js
931 ms
jquery.parallax.min.js
1100 ms
jquery.waypoints.min.js
1055 ms
jquery.fittext.min.js
1025 ms
ut-init.js
1282 ms
jquery.isotope.perfectmasonry.min.js
1320 ms
jquery.images.loaded.min.js
1291 ms
jquery.utmasonry.js
1534 ms
ut.effects.js
1532 ms
player
258 ms
lolo3.png
1544 ms
ut-mute.png
1545 ms
IMG_6055.jpg
1566 ms
PRESENT580.jpg
1563 ms
pe580x.jpg
1874 ms
eyes580.jpg
1767 ms
Screen-Shot-2013-12-26-at-14.21.17.png
1881 ms
Screen-Shot-2013-12-26-at-14.01.28.png
1897 ms
dark-arrows.png
1833 ms
raleway-regular-webfont.woff
2330 ms
raleway-semibold-webfont.woff
2405 ms
raleway-medium-webfont.woff
2478 ms
fontawesome-webfont.svg
2533 ms
fontawesome-webfont.woff
2593 ms
cropped.jpg
2586 ms
overlay-pattern2.png
2779 ms
220 ms
33 ms
interstate-0ab59479718c8235122cad6b16a66953d725c43a.css
240 ms
widget-0511d506.css
71 ms
widget-d9304090.js
155 ms
logo-200x120-177df3dd.png
38 ms
ga.js
90 ms
visual-multi-sounds-6b214103.js
159 ms
error-698b3c1d.js
70 ms
__utm.gif
38 ms
beacon.js
151 ms
__utm.gif
135 ms
logo_grey-377f1b9e.png
126 ms
ga.js
249 ms
lolo3.png
1079 ms
PRESENT580.jpg
1076 ms
pe580x.jpg
1078 ms
eyes580.jpg
1079 ms
Screen-Shot-2013-12-26-at-14.21.17.png
1078 ms
Screen-Shot-2013-12-26-at-14.01.28.png
1142 ms
__utm.gif
12 ms
ut-mute.png
89 ms
IMG_6055.jpg
138 ms
dark-arrows.png
134 ms
cropped.jpg
108 ms
overlay-pattern2.png
100 ms
pandreyez.com accessibility score
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
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.
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.
pandreyez.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
pandreyez.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pandreyez.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Pandreyez.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.
pandreyez.com
Open Graph description is not detected on the main page of PANDR EYEZ. 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: